-
Notifications
You must be signed in to change notification settings - Fork 201
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
Make digital pin traits fallible #97
Closed
Closed
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
227468b
Make InputPin trait methods fallible
eldruin 611ec43
Add documentation for InputPin Error type
eldruin 2e90b03
Add FallibleOutputPin trait
eldruin 7c2167b
Make ToggeableOutputPin fallible
eldruin 156c861
Fix unwrapping toggle result in example
eldruin 34cd2b8
Fix spacing
eldruin db447ce
Add ToggleableOutputPin change to changelog
eldruin e959f02
Put fallible OutputPin behind use-fallible-digital-traits feature
eldruin f873a73
Make StatefulOutputPin inherit from OutputPin to inherit its error type
eldruin 2a1d72e
Mark infallible digital traits as deprecated
eldruin b681162
Update changelog
eldruin 2bad26e
Add missing import
eldruin ea14b73
Prioritize fallible version
eldruin 623aaf8
Split implementations to leave infallible traits untouched though dep…
eldruin 2ab76fe
Add use-fallible-digital-traits to travis matrix
eldruin 6224d88
Implement fallible digital traits as a clean break
eldruin 3422af2
Remove builds with use-fallible-digital-traits feature
eldruin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
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.
Hmm, I'm wondering, if we should simplify the example. I mean, we want people to use the new fallible versions, so why even show the infallible versions here? Thoughts?
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.
I agree that the docs should prioritise the fallible version, though maybe we could keep the infallible documentation until the opt-out release?
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.
I moved the fallible versions up. However, the example still looks quite cluttered with
#cfg...
to me. Any ideas?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.
It is a bit cluttered, maybe grouping each example would help?
I'm ok with merging this either way.
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.
I found no way to group the statements so that I can have fewer
#cfg
s. Do you have an idea?