Jai-Community-Library VS cppcoro

Comparatively

> Incremental rebuilds cause a lot of compilation problems, bugs, and errors. Incremental rebuilds are also slow due to the amount of in between files generated between builds. Jai will contain no incremental rebuild steps. All will be compiled in one fresh compilation. This means that the compiler will need to run fast with high performance. The eventual goal is to compile a 1 million lines of code in 1 second, but as of right now, the compiler can only do 250,000 lines in 1 second.

https://github.com/Jai-Community/Jai-Community-Library/wiki/...

Either ask very politely for years, or be in denial like half the Jai community that writes Jai but is never able to compile it.

Yes, there is a whole Jai community wiki made from half cobbled together knowledge (https://github.com/Jai-Community/Jai-Community-Library/wiki), and a super secret discord made for the super elite, non-compiler-having plebs are banned.

- Philosophical approaches behind project or lack thereof.

Now on the personal, subjective note, the more I look, the more I want to avoid V and get my hands on Jai [1][2]

[1] https://github.com/Jai-Community/Jai-Community-Library/wiki/...

Here's a community wiki that's been kept up-to-date https://github.com/Jai-Community/Jai-Community-Library/wiki

Also this one: https://github.com/Jai-Community/Jai-Community-Library/wiki

There is also the Jai community library, which contains pretty much all the information about the language currently. https://github.com/Jai-Community/Jai-Community-Library

PS: Take a look at cppcoro; this might help as well, especially generator<>, if you're looking to generate numbers, and stuff;

This is the only viable implementation.

Kind of sounds like whatever library you were using provided leaky abstractions. Something like cppcoro provides really good abstractions for coroutines, the user really doesn't need to understand why any of it works.

Is there a usecase for copying/serializing such coroutines? If not, I would use the normal C++20 coroutines (cppcoro?).

C++ has the popular CppCoro library. Async_mutex is its equivalent of Tokio::sync::Mutex, providing exclusive access to data shared between tasks.

Because the whole application is running under a single thread there is no need for atomic operations in synchronization primitives(which most of the time requires seq_cst memory order and CMPXCHG which is an expensive instruction in CPU). for example what async_mutex would look like if it knows it's running in a single-threaded scheduler (a non-atomic state variable and waiters queue).

Maybe not old, but I wish cppcoro was still updated. It was such a nice start!

You can get generator<> from https://github.com/lewissbaker/cppcoro

It is possible to compose them more easily than described in the article; Lewis Baker's cppcoro library for example provides a recursive_generator<> type[0] that allows this without using any macros. It's up to the library part of coroutines to make things easy, end users are not expected to write low-level coroutine code themselves.

I wonder about the allocation elision. Return value optimization became mandatory, and some compilers can already elide calls to new/delete and malloc()/free() in normal code, so perhaps it will be possible to guarantee allocation elision in the future in the most used cases.

[0]: https://github.com/lewissbaker/cppcoro#recursive_generatort