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
Support PREPL format #5
Comments
@raymcdermott is the description of the issue accurate enough? |
This issue is now published on WorksHub. If you would like to work on this issue you can |
@Verdinjoshua26 started working on this issue via WorksHub. |
A user started working on this issue via WorksHub. |
1 similar comment
A user started working on this issue via WorksHub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
suggested by @raymcdermott
The motivation
I would like the same client code for the remote PREPL and the self-hosted PREPL
it’s just trying to make things conform to some standard mechanisms
so that whatever works with the other PREPLs will also work self-hosted
The implemenation details
that we could make a wrapper around the js/eval stuff that back the same data as the PREPL
the way I think about it is that the socket server is just a means to connect to a REPL
and the PREPL can distinguish between output and values <--- the main point of PREPL imho
so you only ever get one value per eval
so we need some key per eval (can just be a simple atom counter)
and then no interleaving
or something like that
main thing is I want to be able to use the PREPL data structures in bootstrapped CLJS
Here is a spec for a PREPL map:
each
:form
must be evaluated and assigned a:val
klipse-clj
should add a new eval function that returns a list of maps (and it will work because each map will have a:form
and a tag (eg:ret
or:out
) and a:val
)The text was updated successfully, but these errors were encountered: