Github action to build documentation

Sweet! I documented workflow files in my "NimSetup" repository (just my obsidian md files regarding various boring technical stuff such as setting up workflows). Generally in terms of feature feedback I'd have the following desires: * Is it possible to have the action do builds in a way that

Cosmo3 multi-os fat binaries with threads

Also, with ORC we don't do any stack marking anymore so coroutines should work much better than when coro.nim was written.

Github action to build documentation

I made a Github action to make all my docs building be done in CI and thought I'd share it in case anyone is interested Can be added to an existing workflow by adding this step (Full working example is in the repo's readme) - name:

Cosmo3 multi-os fat binaries with threads

Have you seen the coro module in the standard library? Sounds like it might be of interest to you:

Cosmo3 multi-os fat binaries with threads

If one wants to implement coroutines in pure C, setjmp and longjmp is probably not the thing to use as it does not allow to have a separate C stack for each coroutine. One should probably use makecontext and swapcontext on stacks allocated with mmap (with MAP_GROWSDOWN, lighter than malloc). [c

NIR

I would assume it's nimsuggest which hangs. It's compiled into NimLSP, so it's one process. If you run the nimlsp_debug binary it starts logging stuff, including nimsuggest equivalent commands you can try in nimsuggest and see if it hangs the same way.

is jester now working well with nim version 2

thanks alot i will do well to share what i finally build with jester here.it worked well.

is jester now working well with nim version 2

Jester is working fine, but httpbeast is missing a new tag-release on GitHub to work with Nim v2. See workaround in this [issue](https://github.com/dom96/jester/issues/321#issuecomment-1685240892). You can compile with `nim c -d:dev -d:useStdLib -r server.nim` where -`d:useStdLib` forces jester

is jester now working well with nim version 2

i tried to use jester with the latest nim sometimes ago. but it never compiled.

NIR

the only way to use NimLSP with vscode currently is until gets done when using it with large projects, or just large files (like the ones generated by Futhark), or just by

Cosmo3 multi-os fat binaries with threads

I found this article very insightful around the async problem: > What language isn’t colored? > > [...] Three more languages that don’t have this problem: Go, Lua, and Ruby. > > Any guess what they have in common? > >

NIR

The problem is that NimLSP does more than just returning error messages like `nim check` does. For example goto definition, hover information, auto-complete, etc. I'm all for improving NimLSP, but throwing out `nimsuggest` for `nim check` would be a big step backwards. Hit me up on Discord/Matr

how to feed stdin to external process and redirect stdout ?

The trickier parts of any approach in this vein arises when keeping alive the "companion process" to your reader and IPC is a big topic { [Here are some slides](https://nmsl.cs.nthu.edu.tw/wp-content/uploads/2011/09/images_courses_CS5432_2016_15-classipc.pdf) and [cligen/osUt](https://github.co

NIR

After the NIR-AST mapping, _Not-nil checking and static array index bounds checking_ should come next. This should be followed by: _Better borrow checker to refine the "view types" implementation._ I think the REPL and new C++ back-end are only nice-to-have.

NIR

A high quality REPL is a killer feature which almost all other "new" languages lack. I'll wager my 2 cents on that one.