We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Round
Round has several methods that deal with the round's position in the state transition graph:
id(&self) -> RoundId
fn possible_next_rounds(&self) -> BTreeSet<RoundId>
fn returns_result(&self) -> bool
Similarly, there are three methods dealing with how the node interacts with other nodes during the round (intersects with #4):
fn message_destinations(&self) -> &BTreeSet<Id>
fn expecting_messages_from(&self) -> &BTreeSet<Id>
fn echo_round_participation(&self) -> EchoRoundParticipation<Id>
Does it make sense to merge either of the group into one method returning an enum? Which possibilities do we need to cover?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Round
has several methods that deal with the round's position in the state transition graph:id(&self) -> RoundId
,fn possible_next_rounds(&self) -> BTreeSet<RoundId>
,fn returns_result(&self) -> bool
.Similarly, there are three methods dealing with how the node interacts with other nodes during the round (intersects with #4):
fn message_destinations(&self) -> &BTreeSet<Id>
,fn expecting_messages_from(&self) -> &BTreeSet<Id>
,fn echo_round_participation(&self) -> EchoRoundParticipation<Id>
.Does it make sense to merge either of the group into one method returning an enum? Which possibilities do we need to cover?
The text was updated successfully, but these errors were encountered: