-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
unfeature-gate tuple-indexing, then replace tuple indexing traits / methods accordingly #18006
Comments
Note that as-is today we can't deprecate these traits due to tuple indexing being behind a feature gate. In other words, this issue may want to rather be a simultaneous execution of un-feature-gating and deprecating the tuple traits. |
As @alexcrichton says, with tuple-indexing behind a feature gate, it would be bad to remove the tuple-accessor traits/methods until it has been unfeature-gated. So we are planning to leave the |
P-high |
Does the community have consensus on making tuple_indenxing accepted (i.e. ungated)? I have seen the RFC but found no info about that. |
Ok, I just found out about this RFC 450 which ask to un-gate tuple indexing, thus blocking this issue. |
r? @alexcrichton or anyone else closes #18006
r? @alexcrichton or anyone else closes #18006
…ykril Provide an option to hide deprecated items from completion Fixes rust-lang#17989. I wonder if this should be instead done in the editor, that will do it in a language-agnostic way. Can't hurt to do it in rust-analyzer, I guess.
These traits have been marked
#[stable]
so this is a backwards compatibility issue, but it will be trivial to replace these.The text was updated successfully, but these errors were encountered: