{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":724712,"defaultBranch":"master","name":"rust","ownerLogin":"rust-lang","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2010-06-16T20:39:03.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5430905?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715473025.0","currentOid":""},"activityList":{"items":[{"before":"1a7397988684934ae01a71f524bdfff24895d8cc","after":"9b75a4388143a163b77fa7d458e4aa4dd34ac1bd","ref":"refs/heads/master","pushedAt":"2024-05-18T00:02:55.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #123865 - eholk:expr_2021, r=fmease\n\nUpdate `expr` matcher for Edition 2024 and add `expr_2021` nonterminal\n\nThis commit adds a new nonterminal `expr_2021` in macro patterns, and `expr_fragment_specifier_2024` feature flag.\n\nThis change also updates `expr` so that on Edition 2024 it will also match `const { ... }` blocks, while `expr_2021` preserves the current behavior of `expr`, matching expressions without `const` blocks.\n\nJoint work with `@vincenzopalazzo.`\n\nIssue #123742","shortMessageHtmlLink":"Auto merge of #123865 - eholk:expr_2021, r=fmease"}},{"before":"c7716d543191e52ed817b725f2fab54bbd5d2707","after":"1a7397988684934ae01a71f524bdfff24895d8cc","ref":"refs/heads/master","pushedAt":"2024-05-17T20:29:59.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125153 - compiler-errors:opt-poly, r=lcnr\n\n`to_opt_poly_X_pred` -> `as_X_clause`\n\nr? lcnr","shortMessageHtmlLink":"Auto merge of #125153 - compiler-errors:opt-poly, r=lcnr"}},{"before":"550d1b4fb6de23990f4108815c3b1a9d1659e5c4","after":"c7716d543191e52ed817b725f2fab54bbd5d2707","ref":"refs/heads/master","pushedAt":"2024-05-17T18:22:41.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125216 - BoxyUwU:boxy_compiler_rereviews, r=joboet\n\nadd boxy to compiler reviews","shortMessageHtmlLink":"Auto merge of #125216 - BoxyUwU:boxy_compiler_rereviews, r=joboet"}},{"before":"ddba1dc97e83f22165b36dd6158477c49bbbd019","after":"550d1b4fb6de23990f4108815c3b1a9d1659e5c4","ref":"refs/heads/master","pushedAt":"2024-05-17T16:13:36.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125207 - GuillaumeGomez:migrate-rustdoc-scrape-examples-ordering, r=jieyouxu\n\nMigrate `run-make/rustdoc-scrape-examples-remap` to `rmake.rs`\n\nPart of https://github.com/rust-lang/rust/issues/121876.\n\nr? `@jieyouxu`","shortMessageHtmlLink":"Auto merge of #125207 - GuillaumeGomez:migrate-rustdoc-scrape-example…"}},{"before":"a5c37eea5aa922f4d6b543f2d35bdbd892fea2a8","after":"ddba1dc97e83f22165b36dd6158477c49bbbd019","ref":"refs/heads/master","pushedAt":"2024-05-17T13:59:52.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125188 - tgross35:f16-f128-powi, r=Nilstrieb\n\nAdd `powi` fo `f16` and `f128`\n\nThis will unblock adding support to compiler_builtins (), which will then unblock adding tests for these new functions.","shortMessageHtmlLink":"Auto merge of #125188 - tgross35:f16-f128-powi, r=Nilstrieb"}},{"before":"1189851eebdf6b69b164bbb7bf9df91188ae03aa","after":"a5c37eea5aa922f4d6b543f2d35bdbd892fea2a8","ref":"refs/heads/master","pushedAt":"2024-05-17T10:56:58.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125178 - GuillaumeGomez:migrate-rustdoc-with-out-dir, r=jieyouxu\n\nMigrate `run-make/rustdoc-with-out-dir-option` to new `rmake.rs`\n\nPart of https://github.com/rust-lang/rust/issues/121876.\n\nr? `@jieyouxu`","shortMessageHtmlLink":"Auto merge of #125178 - GuillaumeGomez:migrate-rustdoc-with-out-dir, …"}},{"before":"8af67ba01a1b1d95ff375b645ef5a395d3249e09","after":"1189851eebdf6b69b164bbb7bf9df91188ae03aa","ref":"refs/heads/master","pushedAt":"2024-05-17T08:45:36.000Z","pushType":"push","commitsCount":13,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125203 - matthiaskrgr:rollup-5pv7drz, r=matthiaskrgr\n\nRollup of 5 pull requests\n\nSuccessful merges:\n\n - #123694 (expand: fix minor diagnostics bug)\n - #125171 (Rename `flatten(_mut)` → `as_flattened(_mut)`)\n - #125181 (set `rust.channel` properly in source tarballs)\n - #125186 (Remove duplicate word from addr docs)\n - #125191 (Report better WF obligation leaf obligations in new solver)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125203 - matthiaskrgr:rollup-5pv7drz, r=matthiaskrgr"}},{"before":"a26981974230110fa8fb15e1cf04d05b9a2103f9","after":"0436bf18fce724968645d0d2af782ad22f0774d7","ref":"refs/heads/beta","pushedAt":"2024-05-17T06:39:18.000Z","pushType":"push","commitsCount":9,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125183 - cuviper:beta-next, r=cuviper\n\n[beta] backports\n\n- Do not ICE on foreign malformed `diagnostic::on_unimplemented` #124683\n- Fix more ICEs in `diagnostic::on_unimplemented` #124875\n- rustdoc: use stability, instead of features, to decide what to show #124864\n- Don't do post-method-probe error reporting steps if we're in a suggestion #125100\n- Make `non-local-def` lint Allow by default #124950\n\nr? cuviper","shortMessageHtmlLink":"Auto merge of #125183 - cuviper:beta-next, r=cuviper"}},{"before":"fa37db51ac2ba8d20eb88079cb3234d0072c5c3a","after":"8af67ba01a1b1d95ff375b645ef5a395d3249e09","ref":"refs/heads/master","pushedAt":"2024-05-17T04:17:11.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #124129 - lqd:enable-lld, r=Mark-Simulacrum\n\nEnable `rust-lld` on nightly `x86_64-unknown-linux-gnu`\n\nWe believe we have done virtually all the internal work and tests we could to prepare for using `lld` as the default linker (at least on Linux). We're IMHO at a point where we'd need to expand testing and coverage in order to make progress on this effort.\n\nTherefore, for further testing and gathering real-world feedback, unexpected issues and use-cases, this PR enables `rust-lld` as the default linker:\n- on nightly only (and dev channel)\n- on `x86_64-unknown-linux-gnu` only\n- when not using an external LLVM (except `download-ci-llvm`), so that distros are not impacted\n\nas described in more detail in this [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Enabling.20.60rust-lld.60.20on.20nightly.20.60x86_64-unknown-linux-gnu.60/near/433709343).\n\nIn case any issues happen to users, as e.g. lld is not bug-for-bug compatible with GNU ld, it's easy to disable with `-Zlinker-features=-lld` to revert to using the system's default linker.\n\n---\n\nI don't know who should review this kind of things, as it's somewhat of a crosscutting effort. Compiler contributor, compiler performance WG and infra member sounds perfect, so r? `@Mark-Simulacrum.`\n\nThe last crater run encountered a low number (44) of mainly avoidable issues, like small incompatibilities, user errors, and a difference between the two linkers about which default to use with `--gc-sections`. [Here's the triage report](https://hackmd.io/OAJxlxc6Te6YUot9ftYSKQ?view), categorizing the issues, with some analyses and workarounds. I'd appreciate another set of eyes looking at these results.\n\nThe changes in this PR have been test-driven for CI changes, try builds with tests enabled, rustc-perf with bootstrapping, in PR #113382.\n\nFor infra, about the CI change: this PR forces `rust.lld` to false on vanilla LLVM builders, just to make sure we have coverage without `rust-lld`. Though to be clear, just using an external LLVM is already enough to keep `rust.lld` to false, in turn reverting everything to using the system's default linker.\n\ncc `@rust-lang/bootstrap` for the bootstrap and config change\ncc `@petrochenkov` for the small compiler change\ncc `@rust-lang/wg-compiler-performance`\n\nThe blog post announcing the change, that we expect to merge around the same time as we merge this PR, is open [on the blog repo](https://github.com/rust-lang/blog.rust-lang.org/pull/1319).\n\nBootstrap change history: this PR changes the default of a config option on `x86_64-unknown-linux-gnu`. It's, however, not expected to cause issues, or require any changes to existing configurations. It's a big enough change that people should at least know about it, in case it causes unexpected problems. If that happens, set `rust.lld = false` in your `config.toml` (and open an issue).","shortMessageHtmlLink":"Auto merge of #124129 - lqd:enable-lld, r=Mark-Simulacrum"}},{"before":"8c127df75fde3d5ad8ef9af664962a7676288b52","after":"fa37db51ac2ba8d20eb88079cb3234d0072c5c3a","ref":"refs/heads/master","pushedAt":"2024-05-17T02:11:06.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125150 - compiler-errors:uplift-goal, r=lcnr\n\nUplift `Goal` to `rustc_type_ir`\n\nr? lcnr\n\nThis also renames `ToPredicate` to `Uplift`, which is conceptually a helper trait for `Into`-like operations for things that need a `TyCtxt`. This name is based off of the same named trait from a-mir-formality.","shortMessageHtmlLink":"Auto merge of #125150 - compiler-errors:uplift-goal, r=lcnr"}},{"before":"2d89cee6258ed0029268ef33e13cc63e433bd243","after":"8c127df75fde3d5ad8ef9af664962a7676288b52","ref":"refs/heads/master","pushedAt":"2024-05-16T23:24:11.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125163 - ssukanmi:stdarch_arm_crc32, r=Amanieu\n\nfeat: update stdarch submodule for intrinsics on ARM\n\nSubmodule update for stdarch library\n10 commits in c0257c1660e78c80ad1b9136fcc5555b14da5b4c..df3618d9f35165f4bc548114e511c49c29e1fd9b\n2024-04-22 01:24:03 +0200 to 2024-05-14 15:52:07 +0200\n- feat: stabilization for stdarch_aarch64_crc32\n- Add vec_insert and vec_extract\n- Remove libc dependency on Windows by using Win32 to get env vars\n- Add vec_orc\n- Simplify vec_andc implementation\n- Silence unexpected-cfgs\n- Add vec_mul\n- Remove `#![feature(inline_const)]`\n- Add `#[cfg_attr(miri, ignore)]` to tests of intrinsics that cannot be supported by Miri\n- Implement ARM `__ssat` and `__usat` functions\n\nr? Amanieu","shortMessageHtmlLink":"Auto merge of #125163 - ssukanmi:stdarch_arm_crc32, r=Amanieu"}},{"before":"97bf25c8cf6c7c97c851c6e8bc94fd0824885e6f","after":"2d89cee6258ed0029268ef33e13cc63e433bd243","ref":"refs/heads/master","pushedAt":"2024-05-16T18:54:24.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #124728 - beetrees:from-f16-for-f64, r=BurntSushi\n\nRe-add `From for f64`\n\nThis impl was originally added in #122470 before being removed in #123830 due to #123831. However, the issue only affects `f32` (which currently only has one `From<{float}>` impl, `From`) as `f64` already has two `From<{float}>` impls (`From` and `From`) and is also the float literal fallback type anyway. Therefore it is safe to re-add `From for f64`.\n\nThis PR also updates the FIXME link to point to the open issue #123831 rather than the closed issue #123824.\n\nTracking issue: #116909\n\n`@rustbot` label +F-f16_and_f128 +T-libs-api","shortMessageHtmlLink":"Auto merge of #124728 - beetrees:from-f16-for-f64, r=BurntSushi"}},{"before":"4a78c00e227124ff9d5ece2d493472e7325c87d3","after":"97bf25c8cf6c7c97c851c6e8bc94fd0824885e6f","ref":"refs/heads/master","pushedAt":"2024-05-16T16:46:42.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125179 - matthiaskrgr:rollup-wkdwoaj, r=matthiaskrgr\n\nRollup of 5 pull requests\n\nSuccessful merges:\n\n - #124871 (Don't ICE because recomputing overflow goals during find_best_leaf_obligation causes inference side-effects)\n - #125018 (Update linker-plugin-lto.md to include LLVM 18)\n - #125130 (rustdoc-json-types: Document `Id`)\n - #125170 (Uplift `FnSig` into `rustc_type_ir` (redux))\n - #125172 (Fix assertion when attempting to convert `f16` and `f128` with `as`)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125179 - matthiaskrgr:rollup-wkdwoaj, r=matthiaskrgr"}},{"before":"bf8801d36dfd28de7d3b0279b53d38593acdfd14","after":"4a78c00e227124ff9d5ece2d493472e7325c87d3","ref":"refs/heads/master","pushedAt":"2024-05-16T14:31:43.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #124959 - prorealize:update-result-documentation, r=joboet\n\nRefactor examples and enhance documentation in result.rs\n\n- Replaced `map` with `map_err` in the error handling example for correctness\n- Reordered example code to improve readability and logical flow\n- Added assertions to examples to demonstrate expected outcomes","shortMessageHtmlLink":"Auto merge of #124959 - prorealize:update-result-documentation, r=joboet"}},{"before":"b71e8cbaf2c7cae4d36898fff1d0ba19d9233082","after":"bf8801d36dfd28de7d3b0279b53d38593acdfd14","ref":"refs/heads/master","pushedAt":"2024-05-16T12:20:05.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #123337 - workingjubilee:debug-compiler-profile-expectations, r=fmease\n\nInclude line tables in compiler profile\n\nThis profile has only undergone minimal tweaks since it was originally drafted. I asked a number of compiler contributors and they said they set rust.debug explicitly. This was even true for one contributor that set `rust.debug = false`! Almost everyone seems slightly surprised that `rust.debug = true` is not the default.\n\nHowever, adding full debuginfo at this level costs multiple gigabytes! We can still get much better profiling and such by setting `rust.debuginfo-level = \"line-tables-only\"` at the cost of only 150~200 MB on the weight of a fresh build dir from `./x.py check`.","shortMessageHtmlLink":"Auto merge of #123337 - workingjubilee:debug-compiler-profile-expecta…"}},{"before":"1871252fc8bb672d40787e67404e6eaae7059369","after":"b71e8cbaf2c7cae4d36898fff1d0ba19d9233082","ref":"refs/heads/master","pushedAt":"2024-05-16T02:31:33.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #124987 - workingjubilee:macro-metavar-expr-with-a-shorter-len, r=c410-f3r,joshtriplett,joshtriplett\n\nRename `${length()}` to `${len()}`\n\nImplements the rename suggested in https://github.com/rust-lang/rust/pull/122808#issuecomment-2047722187\n> I brought this up in the doc PR but it belongs here – `length` should probably be renamed `len` before stabilization. The latter is de facto standard in the standard library, whereas the former is only used in a single unstable API. These metafunctions aren’t library items of course, but should presumably still be consistent with established names.\n\nr? `@c410-f3r`","shortMessageHtmlLink":"Auto merge of #124987 - workingjubilee:macro-metavar-expr-with-a-shor…"}},{"before":"b21b74b5e673b9102502e8f69f378313d901746c","after":"1871252fc8bb672d40787e67404e6eaae7059369","ref":"refs/heads/master","pushedAt":"2024-05-15T23:49:06.000Z","pushType":"push","commitsCount":13,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125164 - fmease:rollup-s5vwzlg, r=fmease\n\nRollup of 5 pull requests\n\nSuccessful merges:\n\n - #125003 (avoid using aligned_alloc; posix_memalign is better-behaved)\n - #125142 (Migrate `run-make/rustdoc-themes` to new rmake.rs)\n - #125146 (Migrate `run-make/panic-impl-transitive` to `rmake`)\n - #125154 (Small improvements to the documentaion of FnAbi )\n - #125159 (Meta: Allow unauthenticated users to modify `L-*`, `PG-*` and `-Z*` labels)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125164 - fmease:rollup-s5vwzlg, r=fmease"}},{"before":"ade234d5743795423db6cc7cd52541390a088eab","after":"b21b74b5e673b9102502e8f69f378313d901746c","ref":"refs/heads/master","pushedAt":"2024-05-15T17:12:27.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125134 - compiler-errors:negative-traits-are-not-notable, r=fmease\n\nrustdoc: Negative impls are not notable\n\nIn #124097, we add `impl !Iterator for [T]` for coherence reasons, and since `Iterator` is a [notable trait](https://github.com/rust-lang/rust/blob/8387315ab3c26a57a1f53a90f188f0bc88514bca/library/core/src/iter/traits/iterator.rs#L40), this means that all `-> &[_]` now are tagged with a `!Iterator` impl as a notable trait.\n\nI \"fixed\" the failing tests in that PR with 6cbbb8b709a43482847243484ed67131e372ba71, where I just blessed the tests, since I didn't want to mix these changes with that PR; however, don't believe negative impls are notable, and this PR aims to prevent these impls from being mentioned.\n\nIn the standard library, we use negative impls purely to guide coherence. They're not really a signal of anything useful to the end-user. If there ever is a case that we want negative impls to be mentioned as notable, this really should be an opt-in feature.","shortMessageHtmlLink":"Auto merge of #125134 - compiler-errors:negative-traits-are-not-notab…"}},{"before":"3cb0030fe9de01eeacb7c03eeef0c51420798cfb","after":"ade234d5743795423db6cc7cd52541390a088eab","ref":"refs/heads/master","pushedAt":"2024-05-15T14:50:33.000Z","pushType":"push","commitsCount":17,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125144 - fmease:rollup-4uft293, r=fmease\n\nRollup of 6 pull requests\n\nSuccessful merges:\n\n - #124307 (Optimize character escaping.)\n - #124975 (Use an helper to move the files)\n - #125027 (Migrate `run-make/c-link-to-rust-staticlib` to `rmake`)\n - #125038 (Invert comparison in `uN::checked_sub`)\n - #125104 (Migrate `run-make/no-cdylib-as-rdylib` to `rmake`)\n - #125137 (MIR operators: clarify Shl/Shr handling of negative offsets)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125144 - fmease:rollup-4uft293, r=fmease"}},{"before":"a71c3ffce9ca505af27f43cd3bad7606a72e3ec8","after":"3cb0030fe9de01eeacb7c03eeef0c51420798cfb","ref":"refs/heads/master","pushedAt":"2024-05-15T12:42:35.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #123413 - petrochenkov:delegmulti2, r=fmease\n\ndelegation: Implement list delegation\n\n```rust\nreuse prefix::{a, b, c};\n```\n\nUsing design described in https://github.com/rust-lang/rfcs/pull/3530#issuecomment-2020869823 (the lists are desugared at macro expansion time).\nList delegations are expanded eagerly when encountered, similarly to `#[cfg]`s, and not enqueued for later resolution/expansion like regular macros or glob delegation (https://github.com/rust-lang/rust/pull/124135).\n\nPart of https://github.com/rust-lang/rust/issues/118212.","shortMessageHtmlLink":"Auto merge of #123413 - petrochenkov:delegmulti2, r=fmease"}},{"before":"44fa5fd39a1d2af41bd7f43bc246a5e4f6d94696","after":"a71c3ffce9ca505af27f43cd3bad7606a72e3ec8","ref":"refs/heads/master","pushedAt":"2024-05-15T10:34:25.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125032 - compiler-errors:crash-dump-dir, r=onur-ozkan\n\nMake crashes dump mir to build dir\n\nSet `-Zdump-mir-dir` for `crashes`-style tests.\n\nAlternatively, we just remove `tests/crashes/124436.rs`, since if the only way to get it to repro is via `-Zdump-mir`, then maybe it's not worth it to fix.\n\nFixes #125029","shortMessageHtmlLink":"Auto merge of #125032 - compiler-errors:crash-dump-dir, r=onur-ozkan"}},{"before":"9e7aff794539aa040362f4424eb29207449ffce0","after":"44fa5fd39a1d2af41bd7f43bc246a5e4f6d94696","ref":"refs/heads/master","pushedAt":"2024-05-15T08:26:55.000Z","pushType":"push","commitsCount":10,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125136 - matthiaskrgr:rollup-ljm15m3, r=matthiaskrgr\n\nRollup of 4 pull requests\n\nSuccessful merges:\n\n - #124990 (Also expand weak alias tys inside consts inside `expand_weak_alias_tys`)\n - #125108 (coverage: `CoverageIdsInfo::mcdc_bitmap_bytes` is never needed)\n - #125132 (Add `on_unimplemented\" typo suggestions)\n - #125135 (Fix the dedup error because of spans from suggestion)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125136 - matthiaskrgr:rollup-ljm15m3, r=matthiaskrgr"}},{"before":"0160bff4b1bffa241299aba8c8c63e7a3cd871fe","after":"9e7aff794539aa040362f4424eb29207449ffce0","ref":"refs/heads/master","pushedAt":"2024-05-15T04:14:52.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125031 - Oneirical:dynamic-libs, r=jieyouxu\n\nMigrate `run-make/issue-11908` to new `rmake.rs` format\n\nPart of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html).\n\nSet as draft, because I have a few concerns:\n\n- [x] I am not sure if `target().contains(\"darwin\")` is a good way of checking that the target is on OSX.\n- [x] I find it strange that the `dylib` part of the test adapts to different target platforms, but not the `rlib` part. Is `rlib` named the same on all platforms?","shortMessageHtmlLink":"Auto merge of #125031 - Oneirical:dynamic-libs, r=jieyouxu"}},{"before":"8387315ab3c26a57a1f53a90f188f0bc88514bca","after":"0160bff4b1bffa241299aba8c8c63e7a3cd871fe","ref":"refs/heads/master","pushedAt":"2024-05-15T02:09:03.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125084 - Jules-Bertholet:fix-125058, r=Nadrieril\n\n`rustc_hir_typeck`: Account for `skipped_ref_pats` in `expr_use_visitor`\n\nFixes #125058\n\nr? `@Nadrieril`\n\ncc https://github.com/rust-lang/rust/issues/123076\n\n`@rustbot` label A-edition-2024 A-patterns","shortMessageHtmlLink":"Auto merge of #125084 - Jules-Bertholet:fix-125058, r=Nadrieril"}},{"before":"ac385a5af6d9fa8399a0cec799833cd28324abf8","after":"8387315ab3c26a57a1f53a90f188f0bc88514bca","ref":"refs/heads/master","pushedAt":"2024-05-14T20:15:24.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125125 - lovesegfault:opt-dist-specify-rustc-perf, r=Mark-Simulacrum\n\nfeat(tools/opt-dist): allow local builds to specify a rustc-perf checkout\n\nThis is a first step towards allowing `opt-dist` to work in a sandboxed /\nair-gapped environment, as it allows users to bypass the ad-hoc download of\n`rustc-perf`.","shortMessageHtmlLink":"Auto merge of #125125 - lovesegfault:opt-dist-specify-rustc-perf, r=M…"}},{"before":"bdfd941f4dcbe54e0283433ac970febf4092fa6a","after":"ac385a5af6d9fa8399a0cec799833cd28324abf8","ref":"refs/heads/master","pushedAt":"2024-05-14T16:45:21.000Z","pushType":"push","commitsCount":22,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125120 - compiler-errors:rollup-mnjybwv, r=compiler-errors\n\nRollup of 7 pull requests\n\nSuccessful merges:\n\n - #119838 (style-guide: When breaking binops handle multi-line first operand better)\n - #124844 (Use a proper probe for shadowing impl)\n - #125047 (Migrate `run-make/issue-14500` to new `rmake.rs` format)\n - #125080 (only find segs chain for missing methods when no available candidates)\n - #125088 (Uplift `AliasTy` and `AliasTerm`)\n - #125100 (Don't do post-method-probe error reporting steps if we're in a suggestion)\n - #125118 (Use new utility functions/methods in run-make tests)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #125120 - compiler-errors:rollup-mnjybwv, r=compiler-er…"}},{"before":"31026b7fe3e510a646eddeda838d1f0859f892e7","after":"bdfd941f4dcbe54e0283433ac970febf4092fa6a","ref":"refs/heads/master","pushedAt":"2024-05-14T14:39:14.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #123816 - tgross35:f16-f128-mangling, r=michaelwoerister\n\nAdd v0 symbol mangling for `f16` and `f128`\n\nAs discussed at , use the crate encoding to represent new primitives.","shortMessageHtmlLink":"Auto merge of #123816 - tgross35:f16-f128-mangling, r=michaelwoerister"}},{"before":"c45e831d8fcd33d656047ba97d263c4b91a00735","after":"31026b7fe3e510a646eddeda838d1f0859f892e7","ref":"refs/heads/master","pushedAt":"2024-05-14T12:16:21.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125023 - morr0ne:linux-none-target, r=Nilstrieb\n\nAdd x86_64-unknown-linux-none target\n\nAdds a freestanding linux binary with no libc dependency. This is useful for writing programs written only in rust. It is also essential for writing low level stuff like libc or a dynamic linker.\n\nTier 3 policy:\n\n>A tier 3 target must have a designated developer or developers (the \"target maintainers\") on record to be CCed when issues arise regarding the target. (The mechanism to track and CC such developers may evolve over time.)\n\nI will be the designed maintainer for this target\n\n>Targets must use naming consistent with any existing targets; for instance, a target for the same CPU or OS as an existing Rust target should use the same name for that CPU or OS. Targets should normally use the same names and naming conventions as used elsewhere in the broader ecosystem beyond Rust (such as in other toolchains), unless they have a very good reason to diverge. Changing the name of a target can be highly disruptive, especially once the target reaches a higher tier, so getting the name right is important even for a tier 3 target.\n\nThe target triple is consistent with other targets\n\n>Target names should not introduce undue confusion or ambiguity unless absolutely necessary to maintain ecosystem compatibility. For example, if the name of the target makes people extremely likely to form incorrect beliefs about what it targets, the name should be changed or augmented to disambiguate it.\nIf possible, use only letters, numbers, dashes and underscores for the name. Periods (.) are known to cause issues in Cargo.\n\nThere is no confusion with other targets since it explicitly adds \"none\" at the end instead of omitting the environment\n\n>Tier 3 targets may have unusual requirements to build or use, but must not create legal issues or impose onerous legal terms for the Rust project or for Rust developers or users.\n\nThe target does not introduce any unusual requirement\n\n>The target must not introduce license incompatibilities.\n\nThere are no license incompatibilities\n\n> Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).\n\nEverything added is under that license\n\n>The target must not cause the Rust tools or libraries built for any other host (even when supporting cross-compilation to the target) to depend on any new dependency less permissive than the Rust licensing policy. This applies whether the dependency is a Rust crate that would require adding new license exceptions (as specified by the tidy tool in the rust-lang/rust repository), or whether the dependency is a native library or binary. In other words, the introduction of the target must not cause a user installing or running a version of Rust or the Rust tools to be subject to any new license requirements.\n\nThere are no new dependencies\n\n>Compiling, linking, and emitting functional binaries, libraries, or other code for the target (whether hosted on the target itself or cross-compiling from another target) must not depend on proprietary (non-FOSS) libraries. Host tools built for the target itself may depend on the ordinary runtime libraries supplied by the platform and commonly used by other applications built for the target, but those libraries must not be required for code generation for the target; cross-compilation to the target must not require such libraries at all. For instance, rustc built for the target may depend on a common proprietary C runtime library or console output library, but must not depend on a proprietary code generation library or code optimization library. Rust's license permits such combinations, but the Rust project has no interest in maintaining such combinations within the scope of Rust itself, even at tier 3.\n\nThere is no proprietary dependencies\n\n>\"onerous\" here is an intentionally subjective term. At a minimum, \"onerous\" legal/licensing terms include but are not limited to: non-disclosure requirements, non-compete requirements, contributor license agreements (CLAs) or equivalent, \"non-commercial\"/\"research-only\"/etc terms, requirements conditional on the employer or employment of any particular Rust developers, revocable terms, any requirements that create liability for the Rust project or its developers or users, or any requirements that adversely affect the livelihood or prospects of the Rust project or its developers or users.\n\nNo such terms exist for this target\n\n>Neither this policy nor any decisions made regarding targets shall create any binding agreement or estoppel by any party. If any member of an approving Rust team serves as one of the maintainers of a target, or has any legal or employment requirement (explicit or implicit) that might affect their decisions regarding a target, they must recuse themselves from any approval decisions regarding the target's tier status, though they may otherwise participate in discussions.\n\n>This requirement does not prevent part or all of this policy from being cited in an explicit contract or work agreement (e.g. to implement or maintain support for a target). This requirement exists to ensure that a developer or team responsible for reviewing and approving a target does not face any legal threats or obligations that would prevent them from freely exercising their judgment in such approval, even if such judgment involves subjective matters or goes beyond the letter of these requirements.\n\nUnderstood\n\n>Tier 3 targets should attempt to implement as much of the standard libraries as possible and appropriate (core for most targets, alloc for targets that can support dynamic memory allocation, std for targets with an operating system or equivalent layer of system-provided functionality), but may leave some code unimplemented (either unavailable or stubbed out as appropriate), whether because the target makes it impossible to implement or challenging to implement. The authors of pull requests are not obligated to avoid calling any portions of the standard library on the basis of a tier 3 target not implementing those portions.\n\nThe target already implements core. It might be possible in the future to add support for alloc and std by leveraging crates such as [origin](https://github.com/sunfishcode/origin/) and [rustix](https://github.com/bytecodealliance/rustix)\n\n> The target must provide documentation for the Rust community explaining how to build for the target, using cross-compilation if possible. If the target supports running binaries, or running tests (even if they do not pass), the documentation must explain how to run such binaries or tests for the target, using emulation if possible or dedicated hardware if necessary.\n\nI believe the proper docs are added\n\n>Tier 3 targets must not impose burden on the authors of pull requests, or other developers in the community, to maintain the target. In particular, do not post comments (automated or manual) on a PR that derail or suggest a block on the PR based on a tier 3 target. Do not send automated messages or notifications (via any medium, including via `@)` to a PR author or others involved with a PR regarding a tier 3 target, unless they have opted into such messages.\n\n> Backlinks such as those generated by the issue/PR tracker when linking to an issue or PR are not considered a violation of this policy, within reason. However, such messages (even on a separate repository) must not generate notifications to anyone involved with a PR who has not requested such notifications.\n\nUnderstood\n\n> Patches adding or updating tier 3 targets must not break any existing tier 2 or tier 1 target, and must not knowingly break another tier 3 target without approval of either the compiler team or the maintainers of the other tier 3 target.\n\n> In particular, this may come up when working on closely related targets, such as variations of the same architecture with different features. Avoid introducing unconditional uses of features that another variation of the target may not have; use conditional compilation or runtime detection, as appropriate, to let each target run code supported by that target.\n\nNo other targets are effected\n\n>Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.\n\nThe same backends used by other linux targets work without issues","shortMessageHtmlLink":"Auto merge of #125023 - morr0ne:linux-none-target, r=Nilstrieb"}},{"before":"58426f4a5b69d10db1b0ffa017bac25f1b2e801e","after":"c45e831d8fcd33d656047ba97d263c4b91a00735","ref":"refs/heads/master","pushedAt":"2024-05-14T10:06:43.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #124228 - compiler-errors:lint-overcaptures, r=oli-obk\n\nWarn against changes in opaque lifetime captures in 2024\n\nAdds a (mostly[^1]) machine-applicable lint `IMPL_TRAIT_OVERCAPTURES` which detects cases where we will capture more lifetimes in edition 2024 than in edition <= 2021, which may lead to erroneous borrowck errors.\n\nThis lint is gated behind the `precise_capturing` feature gate and marked `Allow` for now.\n\n[^1]: Except when there are APITs -- I may work on that soon\n\nr? oli-obk","shortMessageHtmlLink":"Auto merge of #124228 - compiler-errors:lint-overcaptures, r=oli-obk"}},{"before":"fba5f44bd880b83245f7d30afe55bf745a88cdf0","after":"58426f4a5b69d10db1b0ffa017bac25f1b2e801e","ref":"refs/heads/master","pushedAt":"2024-05-14T07:43:10.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #125026 - Oneirical:clink-tests, r=jieyouxu\n\nMigrate `run-make/c-link-to-rust-va-list-fn` to `rmake`\n\nPart of #121876.\n\nr? `@jieyouxu`","shortMessageHtmlLink":"Auto merge of #125026 - Oneirical:clink-tests, r=jieyouxu"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAETV6ymgA","startCursor":null,"endCursor":null}},"title":"Activity · rust-lang/rust"}