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

Enforce statically that the user can't obtain direct/broadcast messages from a round #54

Closed
fjarri opened this issue Nov 18, 2023 · 1 comment
Closed

Enforce statically that the user can't obtain direct/broadcast messages from a round #54

fjarri opened this issue Nov 18, 2023 · 1 comment
Labels
code quality Making things simpler
Milestone
v1.0.0

Comments

@fjarri
Copy link
Member

fjarri commented Nov 18, 2023

Currently the user requests the message destination list, and then if it is not None, he passes it on to the message-generating method. Can it be made stricter, so that it is not possible to request a message to an arbitrary destination (thus eliminating some possible errors)? Perhaps, instead of the list of destinations, return a list of "message factory" objects? Would we be able to pass them on to the spawned tasks so that the messages can be generated in parallel?
@fjarri fjarri added the code quality Making things simpler label Nov 18, 2023
@fjarri fjarri added this to the v1.0.0 milestone Nov 26, 2023
@fjarri
Copy link
Member Author

fjarri commented Oct 12, 2024

The discussion moved to entropyxyz/manul#4

@fjarri fjarri closed this as completed Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code quality Making things simpler
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
1 participant
@fjarri