-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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 debug_more_non_exhaustive
#127942
Comments
…, r=Noratrieb Implement `debug_more_non_exhaustive` This implements the ACP at rust-lang/libs-team#248, adding `.finish_non_exhaustive()` for `DebugTuple`, `DebugSet`, `DebugList`, and `DebugMap`. Also used this as an opportunity to make some documentation and tests more readable by using raw strings instead of escaped quotes. Tracking issue: rust-lang#127942
…, r=Noratrieb Implement `debug_more_non_exhaustive` This implements the ACP at rust-lang/libs-team#248, adding `.finish_non_exhaustive()` for `DebugTuple`, `DebugSet`, `DebugList`, and `DebugMap`. Also used this as an opportunity to make some documentation and tests more readable by using raw strings instead of escaped quotes. Tracking issue: rust-lang#127942
Rollup merge of rust-lang#127945 - tgross35:debug-more-non-exhaustive, r=Noratrieb Implement `debug_more_non_exhaustive` This implements the ACP at rust-lang/libs-team#248, adding `.finish_non_exhaustive()` for `DebugTuple`, `DebugSet`, `DebugList`, and `DebugMap`. Also used this as an opportunity to make some documentation and tests more readable by using raw strings instead of escaped quotes. Tracking issue: rust-lang#127942
Small bit of feedback as I'm looking through this, but it feels like it might be useful to actually have the Example where it'd be useful: I'm working on a tool to help more easily verify that double-ended iterators are working, and they accumulate their data into a While structs have no order to their fields (and thus, adding to the end is appropriate every time), lists do have relevant order here, and it feels reasonable to put the marker in the middle. For now, I'll just add a |
That is an interesting idea. Are you imagining that this would be something like |
That's pretty much what I was thinking. I hadn't thought of a good name for it, but, yes. |
Feature gate:
#![feature(debug_more_non_exhaustive)]
This is a tracking issue for the
non_exhaustive()
function onfmt::Debug{List, Map, Set, Tuple}
, which provides an easy way to omit fields with..
.Public API
Steps / History
finish_non_exhaustive
toDebugList
,DebugMap
, andDebugTuple
libs-team#248debug_more_non_exhaustive
#127945Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: