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.

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

Swap to associated trait bounds where viable #13

Merged
merged 1 commit into from
Nov 1, 2021

Conversation

ryankurte
Copy link
Member

  • add RadioState and ReceiveInfo associated trait bounds
  • move receive info from mutable argument to returned value using this
  • update blocking, nonblocking, mock to match
  • apply formatting

relates to #12, any opinions @henrikssn?

@henrikssn
Copy link
Member

The change LGTM, is the formatting simply what you get using cargo fmt? In that case, we might want to add a github action that verifies all code is correctly formatted.

I patched this branch into my code base and it all worked fine.

Move info from argument to returned value using this.

Co-authored-by: Rick van der Wal <[email protected]>
@ryankurte ryankurte force-pushed the fix/assoc-type-bounds branch from d4ef65f to f7aa1fa Compare November 1, 2021 18:54
@ryankurte ryankurte merged commit 69ffd3a into master Nov 1, 2021
@ryankurte
Copy link
Member Author

The change LGTM, is the formatting simply what you get using cargo fmt? In that case, we might want to add a github action that verifies all code is correctly formatted.

yep, and this is probably a good idea

@henrikssn
Copy link
Member

The change LGTM, is the formatting simply what you get using cargo fmt? In that case, we might want to add a github action that verifies all code is correctly formatted.

yep, and this is probably a good idea

Done in #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants