-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposals #1
Comments
Planned:
|
|
|
State what is the scope on the support of features beside integrations with other techs. |
Things that will definately be helpful and will fit easily in the current model are in my opinion:
I though of Streams at least twice but I still have very much unclear what api to expose and to what extend streams should be integrated, if you have an example where streams are a solution we can look into it in details. |
As a side note the reason for stating the integrations is to discover better all the needed lower level components and what a good api can look like (for example the RPC integration has helped shaping higher order interpreters) |
Migration to Wave has been merged, next planned is expose apis for Mutex/Semaphore/etc with the proper overloads for env. Also wave has experimental streams implementation that we might leverage too |
…de-14.14.22 Bump @types/node from 14.14.21 to 14.14.22
To discuss ideas, any library you might think should have a wrapper or any ideas for improvements welcome!
The text was updated successfully, but these errors were encountered: