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

Further EXTI cleanups/enhancements #72

Merged
merged 6 commits into from
Jan 13, 2020
Merged

Further EXTI cleanups/enhancements #72

merged 6 commits into from
Jan 13, 2020

Conversation

jonas-schievink
Copy link
Contributor

No description provided.

Copy link
Contributor

@hannobraun hannobraun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @jonas-schievink, this looks good!

Regarding your commit moving the documentation to the trait: I'd much prefer if the trait didn't exist and there was just a struct with a constructor that took ownership of EXTI. This would follow the style of many other peripheral APIs. I don't expect you to do this (your PR is great as-is), but your commit reminded me of that, so I thought I'd mention it.

@hannobraun
Copy link
Contributor

(Travis failure is unrelated to this PR, and already fixed in #66)

@jonas-schievink
Copy link
Contributor Author

Yeah, moving EXTI to a wrapper struct makes sense to me. I think the API was this way because there's no need to initialize anything here (unlike for timers, serial, etc.) so the raw EXTI can be immediately used.

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.

3 participants