-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rolling up PRs in the queue #15163
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
Merged
Merged
Rolling up PRs in the queue #15163
Conversation
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
This adds an implementation of Add for String where the rhs is <S: Str>. The other half of adding strings is where the lhs is <S: Str>, but coherence and the libcore separation currently prevent that.
This breaks a fair amount of code. The typical patterns are: * `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`; * `println!("{}", 3)`: change to `println!("{}", 3i)`; * `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`. RFC rust-lang#30. Closes rust-lang#6023. [breaking-change]
It's unclear what you are supposed to do with this memory. Let's make that more clear.
The rust-lang#14869 removed `TraitStore` from `ty_trait` and represented trait reference as regular `ty_rptr`. An old bug of the missing constraint upon lifetime parameter of trait reference then is fixed as a side effect. Adds tests for affected bugs and closes them. Closes rust-lang#12470. Closes rust-lang#14285.
Rust by Example is far better. Fixes rust-lang#14380.
It was previously assumed that the object file generated by LLVM would always require the __morestack function, but that assumption appears to be incorrect, as outlined in rust-lang#15108. This commit forcibly tells the linker to include the entire archive, regardless of whether it's currently necessary or not. Closes rust-lang#15108
Add support for unit literals to const_eval.
In line with what @brson, @cmr, @nikomatsakis and I discussed this morning, my redux of the tutorial will be implemented as the Guide. This way, I can work in small iterations, rather than dropping a huge PR, which is hard to review. In addition, the community can observe my work as I'm doing it. This adds a note in line with [this comment][reddit] that clarifies the state of the tutorial, and the community's involvement with it. [reddit]: http://www.reddit.com/r/rust/comments/28bew8/rusts_documentation_is_about_to_drastically/ci9c98k
The following are tagged 'unstable' - core::clone - Clone - Clone::clone - impl Clone for Arc - impl Clone for arc::Weak - impl Clone for Rc - impl Clone for rc::Weak - impl Clone for Vec - impl Clone for Cell - impl Clone for RefCell - impl Clone for small tuples The following are tagged 'experimental' - Clone::clone_from - may not provide enough utility - impls for various extern "Rust" fns - may not handle lifetimes correctly See https://github.com/rust-lang/rust/wiki/Meeting-API-review-2014-06-23#clone
This is an unused one-liner.
These are closer to language tests than library.
The following are unstable: - core::int, i8, i16, i32, i64 - core::uint, u8, u16, u32, u64 - core::int::{BITS, BYTES, MIN, MAX}, etc. - std::int, i8, i16, i32, i64 - std::uint, u8, u16, u32, u64 The following are experimental: - std::from_str::FromStr and impls - may need to return Result instead of Option - std::int::parse_bytes, etc. - ditto - std::num::FromStrRadix and impls - ditto - std::num::from_str_radix - ditto The following are deprecated: - std::num::ToStrRadix and imples - Wrapper around fmt::radix. Wrong name (Str vs String) See https://github.com/rust-lang/rust/wiki/Meeting-API-review-2014-06-23#uint
"as this document" should be "than this document"
This commit removes FIXMEs of few closed issues. Closes rust-lang#13992
We only need the temporary when the type needs to be dropped, for other types, we can use trans_into to directly place the value into the destination.
This code deserves a bigger refactor, but here's a local improvement.
bindings. This will break code that incorrectly did things like: fn f(a @ box b: Box<String>) {} Fix such code to not rely on undefined behavior. Closes rust-lang#12534. [breaking-change]
We only need to register them once, and once they're registered twice warnings will start being spewed or worse may happen! Closes rust-lang#14330
Closes rust-lang#14482 (std: Bring back half of Add on String) Closes rust-lang#15026 (librustc: Remove the fallback to `int` from typechecking.) Closes rust-lang#15119 (Add more description to c_str::unwrap().) Closes rust-lang#15120 (Add tests for rust-lang#12470 and rust-lang#14285) Closes rust-lang#15122 (Remove the cheat sheet.) Closes rust-lang#15126 (rustc: Always include the morestack library) Closes rust-lang#15127 (Improve ambiguous pronoun.) Closes rust-lang#15130 (Fix rust-lang#15129) Closes rust-lang#15131 (Add the Guide, add warning to tutorial.) Closes rust-lang#15134 (Xfailed tests for hygiene, etc.) Closes rust-lang#15135 (core: Add stability attributes to Clone) Closes rust-lang#15136 (Some minor improvements to core::bool) Closes rust-lang#15137 (std: Add stability attributes to primitive numeric modules) Closes rust-lang#15141 (Fix grammar in tutorial) Closes rust-lang#15143 (Remove few FIXMEs) Closes rust-lang#15145 (Avoid unnecessary temporary on assignments) Closes rust-lang#15147 (Small improvements for metaprogramming) Closes rust-lang#15153 (librustc: Check function argument patterns for legality of by-move) Closes rust-lang#15154 (test: Add a test for regions, traits, and variance.) Closes rust-lang#15159 (rustc: Don't register syntax crates twice) Closes rust-lang#13816 (Stabilize version output for rustc and rustdoc)
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Jul 17, 2023
fix(metrics): Push to master branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.