-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Replace conditions with dynamically scoped variables #300
Comments
Conditions have long since been removed, so closing. |
Weren't there some use cases for dynamic variables that we were still interested in supporting? I vaguely recall discussion of this at some work week some time ago... |
Perhaps? This is such an old issue I suspect that we would want to reopen a new one anyway though. |
Fair enough. :) |
withoutboats
pushed a commit
to withoutboats/rfcs
that referenced
this issue
Jan 15, 2017
Fix docs typo
wycats
pushed a commit
to wycats/rust-rfcs
that referenced
this issue
Mar 5, 2019
RFC Process Update
wycats
pushed a commit
to wycats/rust-rfcs
that referenced
this issue
Mar 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Friday Nov 22, 2013 at 03:59 GMT
For earlier discussion, see rust-lang/rust#10602
This issue was labelled with: A-libs, B-RFC, P-low in the Rust repository
Conditions are a special case of dynamic scope, and the few conditions we have in std that make sense, like
not_utf8
could simply be represented as a dynamic variable that represents the standard schemes for coping with unicode errors: failure, deletion, replacement char.Nominating.
The text was updated successfully, but these errors were encountered: