Tracking issue for 1.0.0 tracking issues #39954
Comments
|
@SimonSapin btw, you could also have run tidy. It outputs you a list of features and whether they are active or stable. |
|
Interesting, thanks. It looks like the it’s same list, but it doesn’t include tracking issue numbers. |
|
link_llvm_intrinsics is perma-unstable, and so is fundamental IIRC. |
|
@nagisa Ok, edited. Also edited to add library features. New total count: |
|
It'd be great to add this to each of their pages in the unstable book. I have some ideas... |
|
@steveklabnik “this” being which of all unstable features |
|
I'd like some kind of status like this for all of the flags, honestly. It's just these ones that you've done the work for :) |
|
Ah, so you mean tagging which features we are planning to deprecate vs which ones have some chance of eventual stabilization. |
Mark-Simulacrum
added
the
C-tracking-issue
|
Triage: is this obsolete? |
|
That would be ironic |
|
@ishitatsuyuki Depends what you mean. This issue is not yet at the point where it should be closed because every feature that existed 1.0.0 are now either stable or removed. I’ve just gone through checkboxes and made a couple updates, but there are still some that are unchecked. As to whether it’s useful, that’s a different question. When the stability mechanism was introduced some months before 1.0.0 we started out with everything in the standard library and a lot of language features being unstable "by default", then worked on stabilizing (or removing) them one by one. I think it’s mildly interesting to track the progress of that, and in particular to see what’s left and consider why each of those is still blocked. |
|
This issue mentions #[set_stdio] as being of uncertain stabilization future. I got curious and went looking. In #26868 (comment) it was recommended #[set_stdio] not be made stable. Ever. |
|
It looks (based on a quick CTRL-F) like https://rust-lang.github.io/rfcs/2318-custom-test-frameworks.html does not discuss capturing stdout/stderr in tests. I think it’s potentially interesting to discuss the needs for custom test frameworks and potential solutions, but perhaps not in this thread. |
|
visited for T-compiler backlog bonanza. Since all of the issues listed here are themselves tracking issues, and now both compiler and lang team are doing regular backlog bonanzas to work through backlog of features, we do not think this kind of meta-tracking issue is buying as much as it did back in 2017-2019. (We do think it was quite an awesome feat to gather all this info back then though!) closing |
In the months before Rust 1.0, the stability mechanism was introduced. At first all of the standard library was marked as unstable, then features were stabilized one by one.
I was curious what remains from that time that is still unstable today. I got some data by running:
grep 'active.*1\.0\.0", Some' src/libsyntax/feature_gate.rsTo get them out of the way, I expect these feature gates to be made obsolete (deprecated and eventually removed) by procedural macros 2.0 (#38356):
log_syntaxTracking issue forlog_syntax,trace_macros#29598trace_macrosTracking issue forlog_syntax,trace_macros#29598macro_reexportTracking issue formacro_reexportfeature #29638pluginTracking issue for plugin stabilization (plugin,plugin_registrarfeatures) #29597 (removed)plugin_registrarTracking issue for plugin stabilization (plugin,plugin_registrarfeatures) #29597 (removed)custom_attributeTracking issue forcustom_attributefeatures #29642custom_deriveTracking issue forcustom_derivefeature #29644rustc_attrsTracking issue forcustom_attributefeatures #29642quoteTracking issue forquotefeature #29601These have also been proposed for deprecation:
mainTracking issue formainfeature #29634placement_in_syntaxTracking issue for placement new #27779 (feature removed)box_syntaxTracking issue for placement new #27779Tracking issue for box_syntax #49733 (removed)box_patternsTracking issue forbox_patternsfeature #29641These are "permanently unstable":
link_llvm_intrinsicsTracking issue forlink_llvm_intrinsics#29602fundamentalTracking issue forfundamentalfeature #29635Which leaves feature flags dating from 1.0.0, that are still unstable
todayas of 2017-02-19, and that have some likelihood of being stabilized in the future:startTracking issue for thestartfeature #29633link_argsTracking issue forlink_argsstabilization #29596linkageTracking issue for thelinkagefeature #29603asmTracking issue forasm(inline assembly) #29722simdTracking issue for SIMD support #27731simd_ffiTracking issue for SIMD support #27731allocatorTracking issue for changing the global, default allocator (RFC 1974) #27389thread_localTracking issue forthread_localstabilization #29863unboxed_closuresTracking issue for Fn traits (unboxed_closures&fn_traitsfeature) #29625concat_identsTracking issue forconcat_idents#29599non_ascii_identsTracking issue for non-ASCII identifiers (feature "non_ascii_idents") #28979Tracking issue for RFC 2457, "Allow non-ASCII identifiers" #55467optin_builtin_traitsTracking Issue for auto traits (auto_traits) -- formerly called opt-in built-in traits (optin_builtin_traits) #13231on_unimplementedTracking issue foron_unimplementedfeature #29628associated_constsTracking issue forassociated_constsfeature #29646slice_patternsTracking issue for RFC #495 (featuresslice_patternsandadvanced_slice_patterns) #23121advanced_slice_patternsTracking issue for RFC #495 (featuresslice_patternsandadvanced_slice_patterns) #23121(Individual features should be discussed in their respective tracking issues.)
Edit: I realized that
feature_gate.rsdoes not include library features, so I got more data:And in a checkout of the
1.0.0git tag:Got the intersection (
com -12 /tmp/now /tmp/1.0.0), and looked manually to remove deprecated features and implementation details, and add tracking issue numbers. This leaves these feature flags:allocTracking issue for location of facade crates #27783collectionsTracking issue for location of facade crates #27783 (reexported stable inMerged intostd, but could still be useful with#![no_std])alloc.unicodeTracking issue for location of facade crates #27783 (mostly reexported stable instd)ioTracking issue for Read::chars #27802lookup_hostTracking issue for DNS in std::net #27705set_stdio(No tracking issue! Despite being useful for example to external test harnesses)step_byTracking issue forstep_bystabilization #27741step_traitTracking issue forTracking issue forstep_bystabilization #27741step_traitstabilization #42168nonzeroTracking issue forNonZero/Unique/Sharedstabilization #27730The text was updated successfully, but these errors were encountered: