-
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 7 pull requests #95889
Rollup of 7 pull requests #95889
Conversation
…ons. For those consts and functions, only the summary is kept and a reference to the `char` associated const/method is included. Additionaly, re-exported functions have been converted to function definitions that call the previously re-exported function. This makes it easier to add a deprecated attribute to these functions in the future.
This commit suggests replacing typeof(...) with an actual type of "...", for example in case of `typeof(1)` we suggest replacing it with `i32`. If the expression - Is not const (`{ let a = 1; let _: typeof(a); }`) - Can't be found (`let _: typeof(this_variable_does_not_exist)`) - Or has non-suggestable type (closure, generator, error, etc) we don't suggest anything.
…ds, r=Mark-Simulacrum Avoid duplication of doc comments in `std::char` constants and functions For those consts and functions, only the summary is kept and a reference to the `char` associated const/method is included. Additionaly, re-exported functions have been converted to function definitions that call the previously re-exported function. This makes it easier to add a deprecated attribute to these functions in the future.
…, r=compiler-errors Suggest replacing `typeof(...)` with an actual type This PR adds suggestion to replace `typeof(...)` with an actual type of `...`, for example in case of `typeof(1)` we suggest replacing it with `i32`. If the expression 1. Is not const (`{ let a = 1; let _: typeof(a); }`) 2. Can't be found (`let _: typeof(this_variable_does_not_exist)`) 3. Or has non-suggestable type (closure, generator, error, etc) we don't suggest anything. The 1 one is sad, but it's not clear how to support non-consts expressions for `typeof`. _This PR is inspired by [this tweet]._ [this tweet]: https://twitter.com/compiler_errors/status/1511945354752638976
…r, r=fee1-dead Suggest adding a local for vector to fix borrowck errors closes rust-lang#95574
…lacrum Check for git submodules in non-git source tree. People occasionally download the source from https://github.com/rust-lang/rust/releases, but those source distributions will not work because they are missing the submodules. They will get a confusing `failed to load manifest for workspace member` error. Unfortunately AFAIK there is no way to disable the GitHub source links. This change tries to detect this scenario and provide an error message that guides them toward a solution. Closes rust-lang#95608
…, r=Dylan-DPC Fix missing space in lossy provenance cast lint See rust-lang#95599 (comment)
Allow multiple derefs to be splitted in deref_separator Previously in rust-lang#95649 only a single deref within projection was supported and multiple derefs caused a bunch of issues, this PR fixes those issues. ```@oli-obk``` helped a ton again ❤️
…laumeGomez rustdoc: Reduce allocations in a `html::markdown` function
@bors r+ rollup=never p=5 |
📌 Commit fcfecab has been approved by |
⌛ Testing commit fcfecab with merge f2807a2ba61fab665488b2e9f646fd9e3b92593a... |
💔 Test failed - checks-actions |
@bors retry |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (1f7fb64): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Since this is a fairly small regression, and given this is a rollup likely not worth the time to investigate -- benefit/cost tradeoff is not worth it. It's not clear that it's consistent either -- there's not a strong enough signal on one benchmark for me to fully trust it's real. @rustbot label +perf-regression-triaged |
Successful merges:
std::char
constants and functions #95566 (Avoid duplication of doc comments instd::char
constants and functions)typeof(...)
with an actual type #95784 (Suggest replacingtypeof(...)
with an actual type)html::markdown
function #95868 (rustdoc: Reduce allocations in ahtml::markdown
function)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup