Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Avoid dependency on consumed message type, generate a marker type #11

Open
Tracked by #7
drahnr opened this issue Oct 5, 2022 · 0 comments
Open
Tracked by #7

Avoid dependency on consumed message type, generate a marker type #11

drahnr opened this issue Oct 5, 2022 · 0 comments

Comments

@drahnr
Copy link
Collaborator

drahnr commented Oct 5, 2022 •
edited
Loading

The generated code strongly relies on the consumed message type, which complicates the generated code significantly. Using a marker type and additional trait to annotate sent and consumed types, would likely be advantageous to reduce complexity and have one defining information anchor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@drahnr