amano-kenji

The fact that janet API doesn't document things thoroughly doesn't mean it's the right way. The fact that something has been done in a certain way doesn't mean it can't...

If janet ships with something like info manual, then `(doc os/proc-kill)` and `(doc os/proc-close)` can refer people to the info manual section on subprocess management. Offline documentation should be as...

Even if the website has a section on subprocess management, there is no guarantee that people will read it or start there. Many people may start using functions directly. Then,...

My rough idea is that janet can ship with offline documentation and `(doc os/proc-kill)` can mention > Read (help subprocess-management) for details. or > function doc string > ... >...

Okay.

With `epoll=false`, the following code causes segmentation fault. ```janet (import spork/sh) (def devnull (sh/devnull)) (ev/spawn-thread (ev/write devnull "ok")) ``` Welcome to hell.

I built the latest commit with `epoll=false`, and this issue can still be reproduced with the sample code above.

At least, the segmentation fault is gone now. The 100% cpu usage is not gone, yet.

I tested the latest commit, and the issue seems fixed.

Is it difficult to implement `stdin` as `core/stream`?