-
Notifications
You must be signed in to change notification settings - Fork 230
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 traits fallible #105
Conversation
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.
looks great to me, thanks @eldruin! (and sorry for all the sidetracking)
cc. @hannobraun
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.
Looks good to me! Thank you @eldruin for all your great work, and sorry for the back and forth. This is a hard project to maintain and contribute to :)
I'm fine with merging this, but there's discussion in #92 about releasing a last 0.2.x release before merging breaking changes. |
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.
Sorry, @eldruin, there's going to be more back and forth. My proposal to make a clean break here was possibly wrong. At the very least, it was premature to assume this discussion was resolved and we can go ahead here. I've become convinced we need to block this pull request until we've decided on a transition strategy in #100, or at least until we've given everyone more time to comment on my proposal to make a clean breaking change.
More context: #92 (comment)
This makes the digital traits fallible as discussed in #97, #95, #100 and #41 implemented as a clean break.