-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Experiment: Add where T: Default
to Default for [T; 0]
impl.
#145457
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
base: master
Are you sure you want to change the base?
Conversation
@bors try |
Experiment: Add `where T: Default` to `Default for [T; 0]` impl.
This comment has been minimized.
This comment has been minimized.
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
There was some discussion of this crater run on IRLO. |
…-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, rust-lang#145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, rust-lang#146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
…-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, rust-lang#145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, rust-lang#146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
…-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, rust-lang#145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, rust-lang#146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
…-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, rust-lang#145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, rust-lang#146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
…-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, rust-lang#145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, rust-lang#146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
Rollup merge of #146533 - Zalathar:array-default, r=compiler-errors Note some previous attempts to change the Default impl for `[T; 0]` Recently, #145457 experimented with changing the Default impl for `[T; 0]`. Subsequently, #146531 also aimed to perform a similar experiment. It seems like a good idea to add some links to the relevant source code, so that the historical context of this tricky topic is easier to find.
Not to be merged; just an experiment.
I'm curious how many crates rely on the
Default for [T; 0]
implementation not having aT: Default
bound. Let's do a crater check run to find out. :)