-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix(swarm-derive): add bounds to OutEvent
on generic fields
#3393
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jxs
force-pushed
the
fix-macro-generics
branch
from
January 26, 2023 22:27
9361a9f
to
bc86fbf
Compare
I think the |
for generic types when out_event was not provided. Previously The enum generated didn't have the NetworkBehaviour impl constraints whilst using the generics for <Generic>::OutEvent.
jxs
force-pushed
the
fix-macro-generics
branch
from
January 27, 2023 12:34
fbc639f
to
2e1638d
Compare
thomaseizinger
changed the title
fix(swarm_derive): Fix derive macro for structures with generic fields
fix(swarm-derive): Fix derive macro for structures with generic fields
Feb 1, 2023
thomaseizinger
approved these changes
Feb 1, 2023
.map(|where_clause| quote! {#where_clause, #(#additional_debug),*}); | ||
|
||
let match_variants = fields.map(|(variant, _ty)| variant); | ||
let msg = format!("`NetworkBehaviour::OutEvent` produced by {name}."); |
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.
👍
thomaseizinger
changed the title
fix(swarm-derive): Fix derive macro for structures with generic fields
fix(swarm-derive): add required bounds to Feb 1, 2023
OutEvent
on generic fields
thomaseizinger
changed the title
fix(swarm-derive): add required bounds to
fix(swarm-derive): add bounds to Feb 1, 2023
OutEvent
on generic fieldsOutEvent
on generic fields
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR isolates the bugfix for the
NetworkBehaviour
derive implementation for structures with generic fields. Whenout_event
was not provided, the generated enum was missing theNetworkBehaviour
impl constraint for the generic variants whilst using the generics for<Generic>::OutEvent
.Meanwhile I also found that the generated
poll
functionloop
s the sub behaviours and eitherreturn
's whenPoll::Ready
orbreak
's whenPoll::Pending
. This is a relict from when we still hadNetworkBehaviourEventProcess
which had added a branch within this loop that did notreturn
but consume the event andcontinue
. This trait was removed a while ago meaning thisloop
is no longer needed.Notes
code generated by the ping example:
Links to any relevant issues
Open Questions
Change checklist