-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rename double_check
to both
#38
Comments
I'm open to being persuaded that this change might be worth it, but at this point, I don't see the value of switching to something shorter or "cleaner" justifying a breaking change here. I actually think that I'll leave this ticket open for a while to hear a counterargument. However, be warned that I might be a tough person to sell this particular suggestion to -- this feels like bikeshedding to me, and I'd just as soon not spend my spare time doing that. |
I agree that this is bikeshedding, but looks are important if we want to sell this particular bikeshed to Rust core and external projects. I can't justify dropping support for Having a shorter keyword for invariant becomes more important when you throw in modifiers to support conditionals (like debug|release assert|expect pre|post|both (y) {
y - 1 == x => "error message";
} At that point, one might as well make release, expect, and both defaults that are never used directly. Then "both" would simply serve as a pedagogical tool. Do you idle on IRC or Matrix? I have some other design ideas I think are worth chatting about : ) |
@indolering: More than happy to chat on Matrix; my handle is @ErichDonGubler:matrix.org. Do you happen to be the same user as the one behind the PR OP, incidentally? |
Yup, one is my dev machine and the other is my personal account. |
Matrix (or the UI at least) appears to be case-sensitive, |
invariant
is misleading, butdouble_check
is too verbose. After some thought, I thinkpre/post/both
is cleaner and semantically honest.The text was updated successfully, but these errors were encountered: