-
Notifications
You must be signed in to change notification settings - Fork 214
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
Janet streams and abstract types. #1155
Comments
I don't know of a consensus or docs. Assuming there aren't issues for drafting something along these lines, may be some of the above text is a good start :) |
|
I think it would be helpful to define and document the mandatory set required to implement a stream so producers know what to offer, and consumers know what is safe to call without run time errors. |
Is there any official consensus and/or documentation on the implementation and use of abstract/OO types for streams in Janet?
ev
/ streams seem to offer the:close
,:read
,:chunk
and:write
methods, butnet/
has a bunch more (:flush
,:accept
, etc)net/...
orev/...
functions directly? For example, Spork's HTTP code at this time depends directly onev/...
functions, which makes it hard (impossible) to re-use this code when running on my own stream types.The text was updated successfully, but these errors were encountered: