-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat: Add bidirectional messaging proc-macro-srv prototype #21249
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
feat: Add bidirectional messaging proc-macro-srv prototype #21249
Conversation
0a41ccb to
bb61e2e
Compare
bb61e2e to
376bca9
Compare
339c074 to
57fdf52
Compare
a01d06d to
19e816d
Compare
ChayimFriedman2
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall good code, left some comments.
@Veykril would you like to review this too?
…pe and remove JsonNew
92ae11e to
336f025
Compare
df4a87f to
9b03499
Compare
e04b4bb to
41dade9
Compare
Veykril
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got some smaller thoughts about how stuff is done/organized here but I don't think that needs to be done for this PR, so lets unblock this for now given I have put down most of those thoughts on the zulip thread
This PR adds a bidirectional proc-macro protocol so the server can ask the client for data while expanding a macro . The approach is still synchronous and single-request-at-a-time. The server may emit sub-requests during expansion, the client replies immediately, and the server then finishes with the final response. All messages use the same request id, and stdin/stdout remain strictly ordered. Legacy protocols are untouched