-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 9 pull requests #101716
Rollup of 9 pull requests #101716
Conversation
Currently the documentation of f64::min refers to "IEEE-754 2008" while the documentation of f64::minimum refers to "IEEE 754-2019". Note that one has the format IEEE,hyphen,number,space,year while the other is IEEE,space,number,hyphen,year. The official IEEE site [1] uses the later format and it is also the one most commonly used throughout the codebase. Update all comments and - more importantly - documentation to consistently use the official format. [1] https://standards.ieee.org/ieee/754/4211/
The padding rule was added in 135281e when converting the rule for #main, but didn't do anything even then.
…, r=nnethercote Add inline-llvm option for disabling/enabling LLVM inlining In this PR, a new -Z option `inline-llvm` is added in order to be able to turn on/off LLVM inlining. The capability of turning on/off inlining in LLVM backend is needed for testing performance implications of using recently enabled inlining in rustc's frontend (with -Z inline-mir=yes option, rust-lang#91743). It would be interesting to see the performance effect using rustc's frontend inlining only without LLVM inlining enabled. Currently LLVM is still doing inlining no mater what value inline-mir is set to. With the option `inline-llvm` being added in this PR, user can turn off LLVM inlining by using `-Z inline-llvm=no` option (the default of inline-llvm is 'yes', LLVM inlining enabled).
Remove manual <[u8]>::escape_ascii `@rustbot` label: +C-cleanup
Suggest pub instead of public for const type item Fixes rust-lang#101626
Fix naming format of IEEE 754 standard Currently the documentation of f64::min refers to "IEEE-754 2008" while the documentation of f64::minimum refers to "IEEE 754-2019". Note that one has the format IEEE,hyphen,number,space,year while the other is IEEE,space,number,hyphen,year. The official IEEE site [1] uses the later format and it is also the one most commonly used throughout the codebase. Update all comments and - more importantly - documentation to consistently use the official format. [1] https://standards.ieee.org/ieee/754/4211/
Check that the types in return position `impl Trait` in traits are well-formed This effectively duplicates `check_associated_type_bounds`, but that shouldn't be for long, since we're going to remove it once we refactor RPITITs into regular associated items. Fixes rust-lang#101663 --- We don't check ```rust trait Foo { fn bar() -> impl ?Sized; } ``` currently, but that's for a different reason, which is that we don't currently check that a trait function's return type is sized (i.e. `fn bar() -> [u8]` also works in a trait).
… r=lcnr Deny return-position `impl Trait` in traits for object safety Fixes rust-lang#101667
…est-0-10, r=notriddle Update browser UI test 0 10 The biggest change from this browser-ui-test update is the upgrade of the puppeteer version to `17.1.3` (the latest in short). I also added the command `click-with-offset` to still allow us to click on the `[-]` part. cc `@jsha` r? `@notriddle`
…illaumeGomez Rustdoc-Json: Add tests for trait impls.
… r=GuillaumeGomez rustdoc: remove no-op `#search` The margin rule was added in c729e4d to remove an unnecessary left margin that was present on desktop. This desktop-mode margin was itself removed in 135281e. The padding rule was added in 135281e when converting the rule for `#main`, but didn't do anything even then.
@bors r+ rollup=never p=5 |
⌛ Testing commit 9bf89e7 with merge 881c4e9d3de032824d8faa4fc82977983c1a1f7a... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
⌛ Testing commit 9bf89e7 with merge b76d6fc1ed6ad1897e56bc23a390a87b6dfe2e14... |
💔 Test failed - checks-actions |
@bors treeclosed=1000 |
@bors r+ rollup=never p=1001 |
💡 This pull request was already approved, no need to approve it again.
|
🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened. |
@bors treeclosed- |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: a93214ec06 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (7f115e3): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
Successful merges:
impl Trait
in traits are well-formed #101676 (Check that the types in return positionimpl Trait
in traits are well-formed)impl Trait
in traits for object safety #101681 (Deny return-positionimpl Trait
in traits for object safety)#search
#101706 (rustdoc: remove no-op#search
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup