-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Tracking issue for no_debug
feature
#29721
Comments
The If we want to let people avoid stepping into a particular function, something like gcc's "artificial" function attribute is a better idea. I can't think of any other good reason to suppress debug info. If we do decide to stabilize this, we need some checks to make sure the attribute is only applied in places where it's actually supported. |
Is anyone using this? What is the motivation for it existing? Nominating for discussion/FCP (my opinion: deprecate unless someone really wants this). |
A quick GitHub search finds no use of this |
I use it as a workaround for #35566. |
Hear ye, hear ye! This unstable issue is now entering final comment period with the inclination to deprecate and remove -- basically because nobody seems to really want it. @rust-lang/lang members, please check off your name to signal agreement. Leave a comment with concerns or objections. Others, please leave comments. Thanks!
|
Deprecated in #37128, so closing. |
The deprecation landed on 2017-10-27. Can this feature be removed? (It still has an entry at https://doc.rust-lang.org/unstable-book/language-features/no-debug.html.) |
@SimonSapin do it =) |
(Or someone else :) ) |
@nikomatsakis Removal is still valid? I've prepared the branch: /~https://github.com/JohnTitor/rust/tree/no-debug |
Remove the `no_debug` feature Context: rust-lang#29721 (comment) r? @nikomatsakis
Tracks stabilization of
#[no_debug]
.The text was updated successfully, but these errors were encountered: