Rollup of 7 pull requests #78594
Merged
Rollup of 7 pull requests #78594
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
With this commit, the examples for exp_m1 would fail if x.exp() - 1.0 is used instead of x.exp_m1().
With this commit, the examples for ln_1p would fail if (x + 1.0).ln() is used instead of x.ln_1p().
Co-authored-by: Camelid <camelidcamel@gmail.com>
- BTreeMap::len - BTreeMap::is_empty - BTreeSet::len - BTreeSet::is_empty
by using a named struct instead of a closure.
… r=KodrAus Add std::panic::panic_any. The discussion of rust-lang#67984 lead to the conclusion that there should be a macro or function separate from `std::panic!()` for throwing arbitrary payloads, to make it possible to deprecate or disallow (in edition 2021) `std::panic!(arbitrary_payload)`. Alternative names: - `panic_with!(..)` - ~~`start_unwind(..)`~~ (panicking doesn't always unwind) - `throw!(..)` - `panic_throwing!(..)` - `panic_with_value(..)` - `panic_value(..)` - `panic_with(..)` - `panic_box(..)` - `panic(..)` The equivalent (private, unstable) function in `libstd` is called `std::panicking::begin_panic`. I suggest `panic_any`, because it allows for any (`Any + Send`) type. _Tracking issue: #78500_
make exp_m1 and ln_1p examples more representative of use With this PR, the examples for `exp_m1` would fail if `x.exp() - 1.0` is used instead of `x.exp_m1()`, and the examples for `ln_1p` would fail if `(x + 1.0).ln()` is used instead of `x.ln_1p()`.
Strip tokens from trait and impl items before printing AST JSON Fixes rust-lang#78510
x.py setup: Create config.toml in the current directory, not the top-level directory See rust-lang#78509 for discussion. r? @pnkfelix cc @cuviper @Mark-Simulacrum
…schievink validator: Extend aliasing check to a call terminator
Constantify more BTreeMap and BTreeSet functions Just because we can: - `BTreeMap::len` - `BTreeMap::is_empty` - `BTreeSet::len` - `BTreeSet::is_empty` Note that I put the `const` under `const_btree_new`, because I don't think their is a need to create another feature flag for that. cc rust-lang#71835
parser: Cleanup `LazyTokenStream` and avoid some clones by using a named struct instead of a closure. r? @Aaron1011
|
📌 Commit 1873ca5 has been approved by |
bors
added
the
S-waiting-on-bors
|
The queue is standing still again? @bors retry |
|
⌛ Testing commit 1873ca5 with merge 2ff2dccecd1ee2502eece7db0fe7c11c6cf4d2f4... |
|
One of the Apple runners went in 'slow mode' again. :( Let's not wait until it times out. @bors retry |
|
⌛ Testing commit 1873ca5 with merge 81cd59fc5ea6a1a9cacd46a9ae0b9412b7a8afea... |
|
And again.. @bors retry |
|
☀️ Test successful - checks-actions |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Successful merges:
LazyTokenStreamand avoid some clones #78587 (parser: CleanupLazyTokenStreamand avoid some clones)Failed merges:
r? @ghost