也算一个总结, 提醒后来人少走弯路.

• 写入 socket 时的内存管理
  uv_write 函数写网口时, 写入数据的内存必须由你管理, 在 回调函数 uv_write_cb 内部释放. 如果你不信邪, 在 uv_write 执行完以后马上释放, 恭喜你掉坑里了. 我就在这坑里呆了一星期. 因为这么干的结果是, 在 Windows 下一切正常, 在 Linux 下会随机写失败. 估计 Windows 对这块写内存复制了一份以增加安全性, 类 unix 平台就不管你死活了. 这点差异性就足以逼你发疯痛不欲生了.

• 接收数

Example here:
https://github.com/MoarVM/MoarVM/blob/8e078a2fed5225332ed5916d9ce8d3f14954a2fc/src/core/threads.c#L171

The error message appeared during Blin run:

🥞🥞🥞 Testing Benchmark::Plot (new)
⏳ 901 out of 1305 modules processed
🥞🥞🥞 Testing App::Pray (new)
🥞🥞🥞 Testing Cro::HTTP (new)
🥞🥞🥞 Testing Auth::SCRAM (new)
🥞🥞🥞 Testing CPAN::Uploader::Tiny (new)
MoarVM panic: Could not spaw

Split from #403

Can you check that fileno is operating properly?

uv_os_fd_t is a HANDLE on Windows and a typedef int on Unix. We have no test cases and it's unclear if we're binding it in a way that makes sense for all platforms.

https://github.com/luvit/luv/blob/cfd4f38bc7c6482e6a8ebf721e196d16a83ab364/src/handle.c#L182-L189

Links:

• http://docs.libuv.org/en/v1.x/handle.htm

In the Comparison Vignette, path_norm() is said to approximate normalizePath().

It seems that path_norm() is more the equivalent of path_abs() though:

library(fs)
normalizePath(".")
#> [1] "/private/var/folders/5z/rm2h62lj45d332kfpj28c8zm0000gn/T/RtmpdjTe5h/reprex171265ac46d6f"
path_norm(".")
#> .
path_abs(".")
#> /private/var/folders/5z/rm2h62lj45d332kfpj28c8zm0000gn/T

Luv.Loop.run returns a boolean value whose meaning does not seem to be documented and, judging by the examples, in most cases is not used, but usually just ignored.

I would argue that using ignore without any type annotation is very error-prone because it sets the trap for accidental partial application. It should be considered bad style IMO, and therefore should be avoided particularly i

https://www.nuget.org/packages/YamlDotNet/ will be a good start.

Brief

Add right-click menu for showing "forward", "reply", "copy", and so on.

Todo

• Add right-click event to TextButton
  • https://stackoverflow.com/questions/35964208/show-a-qmenu-in-response-to-right-click-in-a-qlabel-possible
• Complete related member function for service "forward", "reply", "copy", and so on.

Questions/suggestions:

1. Is this lib alpha beta or ready to go?

2. Could you create a git repo on Github that we can clone that has a basic server that does some async I/O with this lib? Example git repos that people can clone are super nice because you can get up and running very quickly and you don't need to run some scaffolding tool from the command line.

I come from the land of Node.