Merged
Conversation
Contributor
|
r? @kennytm (rust_highfive has picked a reviewer for you, use r? to override) |
Contributor
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
oli-obk
reviewed
Apr 26, 2018
src/liballoc/vec.rs
Outdated
| @@ -324,7 +324,7 @@ impl<T> Vec<T> { | |||
| #[stable(feature = "rust1", since = "1.0.0")] | |||
| pub fn new() -> Vec<T> { | |||
Contributor
There was a problem hiding this comment.
You forgot the actual change of this PR 😆
kennytm
reviewed
Apr 26, 2018
| #[inline] | ||
| #[stable(feature = "rust1", since = "1.0.0")] | ||
| pub fn new() -> Vec<T> { | ||
| pub const fn new() -> Vec<T> { |
Member
There was a problem hiding this comment.
Please mark this with #[rustc_const_unstable(feature = "const_vec_new")] so we don't need to insta-stable this.
Contributor
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Contributor
|
The test needs |
Contributor
|
This changes the behavior for zero-sized types. Before this change, If we want to preserve the current optimization for zero-sized types, then instead of getting rid of the |
Contributor
|
|
Contributor
Author
|
@alexreg would it be possible to get an ETA on that? What does "very soon" mean exactly? If it will be in the next few weeks or so, then I think it would be worth it to wait for that. Otherwise, we could use the |
Contributor
Author
|
@mbrubeck That approach doesn't quite work: |
Contributor
Contributor
|
If you don't use an intermediate const, then the trick should work. Const if is still ways off. So use the array trick |
Contributor
Contributor
|
Still. the trick works now. No need to block this PR |
Contributor
|
Yeah, I don't dispute that. ;-) |
Contributor
Author
|
Hmm... tidy is segfaulting on my machine, so I can't run tests at the moment... |
Contributor
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Contributor
Author
|
Oh 🤦♂️ |
Contributor
Author
|
@kennytm I think this is ready for another review |
Member
|
@bors r+ |
Collaborator
|
📌 Commit f9f9923 has been approved by |
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Apr 30, 2018
Make `Vec::new` a `const fn`
`RawVec::empty/_in` are a hack. They're there because `if size_of::<T> == 0 { !0 } else { 0 }` is not allowed in `const` yet. However, because `RawVec` is unstable, the `empty/empty_in` constructors can be removed when rust-lang#49146 is done...
bors
added a commit
that referenced
this pull request
Apr 30, 2018
Rollup of 7 pull requests Successful merges: - #50233 (Make `Vec::new` a `const fn`) - #50312 (Add more links in panic docs) - #50316 (Fix some broken links in docs.) - #50325 (Add a few more tests for proc macro feature gating) - #50327 (Display correct unused field suggestion for nested struct patterns) - #50330 (check that #[used] is used only on statics) - #50344 (Update Cargo to 2018-04-28 122fd5be5201913d42e219e132d6569493583bca) Failed merges:
Contributor
impl String {
pub fn new() -> String {
String { vec: Vec::new() }
}
}Given that |
Contributor
|
Good idea! |
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
May 9, 2018
Make `String::new()` const Following the steps of rust-lang#50233 , make `String::new()` a `const fn`.
sugar700
added a commit
to sugar700/rust
that referenced
this pull request
Dec 11, 2018
Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
emilyalbini
added a commit
to emilyalbini/rust
that referenced
this pull request
Dec 12, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
emilyalbini
added a commit
to emilyalbini/rust
that referenced
this pull request
Dec 13, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Dec 13, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Dec 14, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Dec 14, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
emilyalbini
added a commit
to emilyalbini/rust
that referenced
this pull request
Dec 14, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
emilyalbini
added a commit
to emilyalbini/rust
that referenced
this pull request
Dec 15, 2018
Test capacity of ZST vector Initially, rust-lang#50233 accidentally changed the capacity of empty ZST. This was pointed out during code review. This commit adds a test to prevent capacity of ZST vectors from accidentally changing to prevent that from happening again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RawVec::empty/_inare a hack. They're there becauseif size_of::<T> == 0 { !0 } else { 0 }is not allowed inconstyet. However, becauseRawVecis unstable, theempty/empty_inconstructors can be removed when #49146 is done...