{"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:1716682659.0","currentOid":""},"activityList":{"items":[{"before":"0285dab54f87120367f5693174136aff24b74640","after":"1d43fbbc7348f2bd9260d8532bffa02f5bd2c9ac","ref":"refs/heads/master","pushedAt":"2024-06-12T18:14:25.000Z","pushType":"push","commitsCount":27,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126332 - GuillaumeGomez:rollup-bu1q4pz, r=GuillaumeGomez\n\nRollup of 9 pull requests\n\nSuccessful merges:\n\n - #126039 (Promote `arm64ec-pc-windows-msvc` to tier 2)\n - #126075 (Remove `DebugWithInfcx` machinery)\n - #126228 (Provide correct parent for nested anon const)\n - #126232 (interpret: dyn trait metadata check: equate traits in a proper way)\n - #126242 (Simplify provider api to improve llvm ir)\n - #126294 (coverage: Replace the old span refiner with a single function)\n - #126295 (No uninitalized report in a pre-returned match arm)\n - #126312 (Update `rustc-perf` submodule)\n - #126322 (Follow up to splitting core's PanicInfo and std's PanicInfo)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126332 - GuillaumeGomez:rollup-bu1q4pz, r=GuillaumeGomez"}},{"before":"bbe9a9c20bac888efae2c7f033fb6cb3925a65b7","after":"0285dab54f87120367f5693174136aff24b74640","ref":"refs/heads/master","pushedAt":"2024-06-12T15:57:26.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 #125141 - SergioGasquez:feat/no_std-xtensa, r=davidtwco\n\nAdd no_std Xtensa targets support\n\nAdds no_std Xtensa targets. This enables using Rust on ESP32, ESP32-S2 and ESP32-S3 chips.\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\n`@MabezDev` and I (`@SergioGasquez)` will maintain the targets.\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.\n> If possible, use only letters, numbers, dashes and underscores for the name. Periods (.) are known to cause issues in Cargo.\n\nWe follow the same naming convention as other targets.\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 legal issues.\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 licenses\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\nRequirements are not changed for any other target.\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\nThe linker used by the targets is the GCC linker from the GCC toolchain cross-compiled for Xtensa. GNU GPL.\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.\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\nHere is how to build for the target https://docs.esp-rs.org/book/installation/riscv-and-xtensa.html and it also covers how to run binaries on the target.\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 should be affected\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\nIt can produce assembly, but it requires a custom LLVM with Xtensa support (https://github.com/espressif/llvm-project/). The patches are trying to be upstreamed (https://github.com/espressif/llvm-project/issues/4)","shortMessageHtmlLink":"Auto merge of #125141 - SergioGasquez:feat/no_std-xtensa, r=davidtwco"}},{"before":"02c7a5921e3de5c2b3ecb2e0082c1dafce0729a1","after":"bbe9a9c20bac888efae2c7f033fb6cb3925a65b7","ref":"refs/heads/master","pushedAt":"2024-06-12T13:41:16.000Z","pushType":"push","commitsCount":39,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126319 - workingjubilee:rollup-lendnud, r=workingjubilee\n\nRollup of 16 pull requests\n\nSuccessful merges:\n\n - #123374 (DOC: Add FFI example for slice::from_raw_parts())\n - #124514 (Recommend to never display zero disambiguators when demangling v0 symbols)\n - #125978 (Cleanup: HIR ty lowering: Consolidate the places that do assoc item probing & access checking)\n - #125980 (Nvptx remove direct passmode)\n - #126187 (For E0277 suggest adding `Result` return type for function when using QuestionMark `?` in the body.)\n - #126210 (docs(core): make more const_ptr doctests assert instead of printing)\n - #126249 (Simplify `[T; N]::try_map` signature)\n - #126256 (Add {{target}} substitution to compiletest)\n - #126263 (Make issue-122805.rs big endian compatible)\n - #126281 (set_env: State the conclusion upfront)\n - #126286 (Make `storage-live.rs` robust against rustc internal changes.)\n - #126287 (Update a cranelift patch file for formatting changes.)\n - #126301 (Use `tidy` to sort crate attributes for all compiler crates.)\n - #126305 (Make PathBuf less Ok with adding UTF-16 then `into_string`)\n - #126310 (Migrate run make prefer rlib)\n - #126314 (fix RELEASES: we do not support upcasting to auto traits)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126319 - workingjubilee:rollup-lendnud, r=workingjubilee"}},{"before":"bdb1b7f5d9715cc96cb437134eff93fa229defd1","after":"02c7a5921e3de5c2b3ecb2e0082c1dafce0729a1","ref":"refs/heads/master","pushedAt":"2024-06-12T11:09: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 #113169 - oli-obk:tait_must_be_constrained_if_in_sig, r=lcnr\n\nTait must be constrained if in sig\n\nr? `@compiler-errors`\n\nkind of reverts https://github.com/rust-lang/rust/pull/62423, but that PR only removed cycles in cases that we want to forbid now anyway.\n\nsee https://rust-lang.zulipchat.com/#narrow/stream/315482-t-compiler.2Fetc.2Fopaque-types/topic/lcnr.20oli.20meeting/near/370712246 for related discussion and motivating example\n\na TAIT showing up in a signature doesn't just mean it can register a hidden type, but that it must.\n\nThis is the [design the types team decided upon](https://hackmd.io/QOsEaEJtQK-XDS_xN4UyQA#Proposal-preferred) for the following reasons\n\n* avoids a hypothetical situation where getting smarter in trait solving could cause new cycle errors or new inference errors to show up, where today something is treated as opaque.\n* avoids having the situation where a (minor?) change to a function body causes an error, because its TAIT usage suddenly isn't \"opaque enough\" anymore.\n* avoids having to explain why in some cases you need to put a Tait into a tiny module together with its defining usages. Now you basically gotta always do this, the moment a Tait is in a signature that isn't in the defining scope.\n* avoids false-cycle errors\n* anything diverging from this pattern needs to either\n * move the TAIT declaration and defining function into their own helper sub module\n * use the attributes we'll provide in the future to explicitly opt in or out of being in the defining scope\n\nfixes #117861\n\nreverts #125362 cc `@Nilstrieb` `@joboet`","shortMessageHtmlLink":"Auto merge of #113169 - oli-obk:tait_must_be_constrained_if_in_sig, r…"}},{"before":"76c73827dcd0b363e60b22c3cef64bde4171bf17","after":"bdb1b7f5d9715cc96cb437134eff93fa229defd1","ref":"refs/heads/master","pushedAt":"2024-06-12T08:59:32.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 #126290 - weihanglo:update-cargo, r=weihanglo\n\nUpdate cargo\n\n14 commits in b1feb75d062444e2cee8b3d2aaa95309d65e9ccd..4dcbca118ab7f9ffac4728004c983754bc6a04ff\n2024-06-07 20:16:17 +0000 to 2024-06-11 16:27:02 +0000\n- Add local registry overlays (rust-lang/cargo#13926)\n- docs(change): Don't mention non-existent workspace.badges (rust-lang/cargo#14042)\n- test: migrate binary_name to snapbox (rust-lang/cargo#14041)\n- Bump to 0.82.0; update changelog (rust-lang/cargo#14040)\n- tests: Migrate alt_registry to snapbox (rust-lang/cargo#14031)\n- fix: proc-macro example from dep no longer affects feature resolution (rust-lang/cargo#13892)\n- chore: Bump cargo-util-schemas to 0.5 (rust-lang/cargo#14038)\n- chore(deps): update rust crate pulldown-cmark to 0.11.0 (rust-lang/cargo#14037)\n- fix: remove `__CARGO_GITOXIDE_DISABLE_LIST_FILES` env var (rust-lang/cargo#14036)\n- chore(deps): update rust crate itertools to 0.13.0 (rust-lang/cargo#13998)\n- fix(toml): remove `lib.plugin` key support and make it warning (rust-lang/cargo#13902)\n- chore(deps): update compatible (rust-lang/cargo#13995)\n- fix: using `--release/debug` and `--profile` together becomes an error (rust-lang/cargo#13971)\n- fix(toml): Convert warnings that `licence` and `readme` files do not exist into errors (rust-lang/cargo#13921)\n\nr? ghost","shortMessageHtmlLink":"Auto merge of #126290 - weihanglo:update-cargo, r=weihanglo"}},{"before":"9a7bf4ae947feddac27007cbe26d161f4ff5a910","after":"76c73827dcd0b363e60b22c3cef64bde4171bf17","ref":"refs/heads/master","pushedAt":"2024-06-12T05:43:28.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 #126130 - compiler-errors:goal-relations, r=lcnr\n\nMake `ObligationEmittingRelation`s emit `Goal` rather than `Obligation`\n\nHelps avoid needing to uplift `Obligation` into the solver. We still can't get rid of `ObligationCause`, but we can keep it as an associated type for `InferCtxtLike` and just give it a `dummy` function.\n\nThere's some shuttling between `Goal` and `Obligation` that may be perf-sensitive... Let's see what rust-timer says.\n\nr? lcnr","shortMessageHtmlLink":"Auto merge of #126130 - compiler-errors:goal-relations, r=lcnr"}},{"before":"ebcb862bbb9031c4969c06ec73d44780ea37d0ff","after":"9a7bf4ae947feddac27007cbe26d161f4ff5a910","ref":"refs/heads/master","pushedAt":"2024-06-12T03:04:28.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 #123508 - WaffleLapkin:never-type-2024, r=compiler-errors\n\nEdition 2024: Make `!` fall back to `!`\n\nThis PR changes never type fallback to be `!` (the never type itself) in the next, 2024, edition.\n\nThis makes the never type's behavior more intuitive (in 2024 edition) and is the first step of the path to stabilize it.\n\nr? `@compiler-errors`","shortMessageHtmlLink":"Auto merge of #123508 - WaffleLapkin:never-type-2024, r=compiler-errors"}},{"before":"d0227c6a19c2d6e8dceb87c7a2776dc2b10d2a04","after":"ebcb862bbb9031c4969c06ec73d44780ea37d0ff","ref":"refs/heads/master","pushedAt":"2024-06-12T00:27:14.000Z","pushType":"push","commitsCount":41,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126284 - jieyouxu:rollup-nq7bf9k, r=jieyouxu\n\nRollup of 6 pull requests\n\nSuccessful merges:\n\n - #115974 (Split core's PanicInfo and std's PanicInfo)\n - #125659 (Remove usage of `isize` in example)\n - #125669 (CI: Update riscv64gc-linux job to Ubuntu 22.04, rename to riscv64gc-gnu)\n - #125684 (Account for existing bindings when suggesting `pin!()`)\n - #126055 (Expand list of trait implementers in E0277 when calling rustc with --verbose)\n - #126174 (Migrate `tests/run-make/prefer-dylib` to `rmake.rs`)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126284 - jieyouxu:rollup-nq7bf9k, r=jieyouxu"}},{"before":"3ea5e236ecb4c5f22437059f82d3915d311e4ec0","after":"d0227c6a19c2d6e8dceb87c7a2776dc2b10d2a04","ref":"refs/heads/master","pushedAt":"2024-06-11T22:19:29.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 #125174 - nnethercote:less-ast-pretty-printing, r=petrochenkov\n\nPrint `token::Interpolated` with token stream pretty printing.\n\nThis is a step towards removing `token::Interpolated` (#124141). It unavoidably changes the output of the `stringify!` macro, generally for the better.\n\nr? `@petrochenkov`","shortMessageHtmlLink":"Auto merge of #125174 - nnethercote:less-ast-pretty-printing, r=petro…"}},{"before":"0c960618b56f662d933e8b864cd9632a99174e87","after":"3ea5e236ecb4c5f22437059f82d3915d311e4ec0","ref":"refs/heads/master","pushedAt":"2024-06-11T18:15:13.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 #125736 - Oneirical:run-make-file-management, r=jieyouxu\n\nrun-make-support: add wrapper for `fs` operations\n\nSuggested by #125728.\n\nThe point of this wrapper is to stop silent fails caused by forgetting to `unwrap` `fs` functions. However, functions like `fs::read` which return something and get stored in a variable should cause a failure on their own if they are not unwrapped (as the `Result` will be stored in the variable, and something will be done on that `Result` that should have been done to its contents). Is it still pertinent to wrap `fs::read_to_string`, `fs::metadata` and so on?\n\nCloses: https://github.com/rust-lang/rust/issues/125728\n\ntry-job: x86_64-msvc\ntry-job: i686-mingw","shortMessageHtmlLink":"Auto merge of #125736 - Oneirical:run-make-file-management, r=jieyouxu"}},{"before":"20ba13c38e5b8451b7b09e4009efc9010bfa3f2c","after":"0c960618b56f662d933e8b864cd9632a99174e87","ref":"refs/heads/master","pushedAt":"2024-06-11T15:49:19.000Z","pushType":"push","commitsCount":15,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126274 - jieyouxu:rollup-uj93sfm, r=jieyouxu\n\nRollup of 5 pull requests\n\nSuccessful merges:\n\n - #126186 (Migrate `run-make/multiple-emits` to `rmake.rs`)\n - #126236 (Delegation: fix ICE on recursive delegation)\n - #126254 (Remove ignore-cross-compile directive from ui/macros/proc_macro)\n - #126258 (Do not define opaque types when selecting impls)\n - #126265 (interpret: ensure we check bool/char for validity when they are used in a cast)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126274 - jieyouxu:rollup-uj93sfm, r=jieyouxu"}},{"before":"6a207f4ff28b76147514cfd6acea86db3d148e42","after":"20ba13c38e5b8451b7b09e4009efc9010bfa3f2c","ref":"refs/heads/master","pushedAt":"2024-06-11T13:38:39.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 #125752 - jieyouxu:kaboom, r=Kobzol\n\nrun-make: arm command wrappers with drop bombs\n\nThis PR is one in a series of cleanups to run-make tests and the run-make-support library.\n\n### Summary\n\nIt's easy to forget to actually executed constructed command wrappers, e.g. `rustc().input(\"foo.rs\")` but forget the `run()`, so to help catch these mistakes, we arm command wrappers with drop bombs on construction to force them to be executed by test code.\n\nThis PR also removes the `Deref`/`DerefMut` impl for our custom `Command` which derefs to `std::process::Command` because it can cause issues when trying to use a custom command:\n\n```rs\nhtmldocck().arg().run()\n```\n\nfails to compile because the `arg()` is resolved to `std::process::Command::arg`, which returns `&mut std::process::Command` that doesn't have a `run()` command.\n\nThis PR also:\n\n- Removes `env_var` on the `impl_common_helper` macro that was wrongly named and is a footgun (no users).\n- Bumps the run-make-support library to version `0.1.0`.\n- Adds a changelog to the support library.\n\n### Details\n\nEspecially for command wrappers like `Rustc`, it's very easy to build up\na command invocation but forget to actually execute it, e.g. by using\n`run()`. This commit adds \"drop bombs\" to command wrappers, which are\narmed on command wrapper construction, and only defused if the command\nis executed (through `run`, `run_fail`).\n\nIf the test writer forgets to execute the command, the drop bomb will\n\"explode\" and panic with an error message. This is so that tests don't\nsilently pass with constructed-but-not-executed command wrappers.\n\nThis PR is best reviewed commit-by-commit.\n\ntry-job: x86_64-msvc","shortMessageHtmlLink":"Auto merge of #125752 - jieyouxu:kaboom, r=Kobzol"}},{"before":"336e6ab3b396e1d1eb9b5a2f0bbc1744f4a68244","after":"6a207f4ff28b76147514cfd6acea86db3d148e42","ref":"refs/heads/master","pushedAt":"2024-06-11T11:27:57.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 #126262 - jieyouxu:rollup-g29lo3c, r=jieyouxu\n\nRollup of 5 pull requests\n\nSuccessful merges:\n\n - #125913 (Spruce up the diagnostics of some early lints)\n - #126234 (Delegation: fix ICE on late diagnostics)\n - #126253 (Simplify assert matchers in `run-make-support`)\n - #126257 (Rename `needs-matching-clang` to `needs-force-clang-based-tests`)\n - #126259 (reachable computation: clarify comments around consts)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126262 - jieyouxu:rollup-g29lo3c, r=jieyouxu"}},{"before":"aec67e238d366c4c41373b272f19dd79ff5ec0f0","after":"336e6ab3b396e1d1eb9b5a2f0bbc1744f4a68244","ref":"refs/heads/master","pushedAt":"2024-06-11T09:10:28.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 #126139 - compiler-errors:specializes, r=lcnr\n\nOnly compute `specializes` query if (min)specialization is enabled in the crate of the specializing impl\n\nFixes (after backport) https://github.com/rust-lang/rust/issues/125197\n\n### What\n\nhttps://github.com/rust-lang/rust/pull/122791 makes it so that inductive cycles are no longer hard errors. That means that when we are testing, for example, whether these impls overlap:\n\n```rust\nimpl PartialEq for AnyId {\n fn eq(&self, _: &Self) -> bool {\n todo!()\n }\n}\n\nimpl PartialEq for AnyId {\n fn eq(&self, _: &T) -> bool {\n todo!()\n }\n}\n```\n\n...given...\n\n```rust\npub trait Identifier: Display + 'static {}\n\nimpl Identifier for T where T: PartialEq + Display + 'static {}\n```\n\nThen we try to see if the second impl holds given `T = AnyId`. That requires `AnyId: Identifier`, which requires that `AnyId: PartialEq`, which is satisfied by these two impl candidates... The `PartialEq` impl is a cycle, and we used to winnow it when we used to treat inductive cycles as errors.\n\nHowever, now that we don't winnow it, this means that we *now* try calling `candidate_should_be_dropped_in_favor_of`, which tries to check whether one of the impls specializes the other: the `specializes` query. In that query, we currently bail early if the impl is local.\n\nHowever, in a foreign crate, we try to compute if the two impls specialize each other by doing trait solving. This may itself lead to the same situation where we call `specializes`, which will lead to a query cycle.\n\n### How does this fix the problem\n\nWe now record whether specialization is enabled in foreign crates, and extend this early-return behavior to foreign impls too. This means that we can only encounter these cycles if we truly have a specializing impl from a crate with specialization enabled.\n\n-----\n\nr? `@oli-obk` or `@lcnr`","shortMessageHtmlLink":"Auto merge of #126139 - compiler-errors:specializes, r=lcnr"}},{"before":"fa1681c9f6a66f0240c46c98bfef6209c9d6df23","after":"aec67e238d366c4c41373b272f19dd79ff5ec0f0","ref":"refs/heads/master","pushedAt":"2024-06-11T06:25:34.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 #126113 - Kobzol:ci-native-arm-runner, r=jdno\n\nCI: use a native `arm64` runner\n\nOpening to test if we can use a native GitHub ARM runner instead of the self-hosted one.\n\nThe CI has finished [successfully](https://github.com/rust-lang/rust/actions/runs/9414573751/job/25933776975?pr=126113). It took 1h 29m, which is longer than the previous duration (~1h 10m). This is expected, since we currently use 8 cores on GitHub, rather than 14 cores which are configured for the self-hosted runner.\n\ntry-job: aarch64-gnu","shortMessageHtmlLink":"Auto merge of #126113 - Kobzol:ci-native-arm-runner, r=jdno"}},{"before":"b5b13568fb5da4ac988bde370008d6134d3dfe6c","after":"fa1681c9f6a66f0240c46c98bfef6209c9d6df23","ref":"refs/heads/master","pushedAt":"2024-06-11T04:13:52.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 #125910 - scottmcm:single-use-consts, r=saethlin\n\nAdd `SingleUseConsts` mir-opt pass\n\nThe goal here is to make a pass that can be run in debug builds to simplify the common case of constants that are used just once -- that doesn't need SSA handling and avoids any potential downside of multi-use constants. In particular, to simplify the `if T::IS_ZST` pattern that's common in the standard library.\n\nBy also handling the case of constants that are *never* actually used this fully replaces the `ConstDebugInfo` pass, since it has all the information needed to do that naturally from the traversal it needs to do anyway.\n\nThis is roughly a wash on instructions on its own (a couple regressions, a few improvements https://github.com/rust-lang/rust/pull/125910#issuecomment-2144963361), with a bunch of size improvements. So I'd like to land it as its own PR, then do follow-ups to take more advantage of it (in the inliner, cg_ssa, etc).\n\nr? `@saethlin`","shortMessageHtmlLink":"Auto merge of #125910 - scottmcm:single-use-consts, r=saethlin"}},{"before":"d402830c8a356332de93761d6996faf5a2ca29ca","after":"b5b13568fb5da4ac988bde370008d6134d3dfe6c","ref":"refs/heads/master","pushedAt":"2024-06-10T23:43:29.000Z","pushType":"push","commitsCount":19,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126240 - matthiaskrgr:rollup-ks4o2n9, r=matthiaskrgr\n\nRollup of 9 pull requests\n\nSuccessful merges:\n\n - #126063 (Remove some unused crate dependencies.)\n - #126115 (Fix ICE due to `unwrap` in `probe_for_name_many`)\n - #126159 (ScalarInt: size mismatches are a bug, do not delay the panic)\n - #126184 (interpret: do not ICE on padded non-pow2 SIMD vectors)\n - #126191 (Fix `NonZero` doctest inconsistencies)\n - #126211 (migrate tests/run-make/llvm-outputs to use rmake.rs)\n - #126212 (fix: build on haiku)\n - #126215 (Add explanatory note to async block type mismatch error)\n - #126223 (run-make: add `run_in_tmpdir` self-test)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126240 - matthiaskrgr:rollup-ks4o2n9, r=matthiaskrgr"}},{"before":"a3167859f2fd8ff2241295469876a2b687280bdc","after":"d402830c8a356332de93761d6996faf5a2ca29ca","ref":"refs/heads/master","pushedAt":"2024-06-10T21:19:54.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 #125209 - Kobzol:rfl-ci, r=Mark-Simulacrum\n\nAdd Rust for Linux `auto` CI job\n\nThis PR adds an `auto` CI job that checks if Rust for Linux (RfL) still compiles with the latest version of the compiler and the standard library. If not, we should ideally ping the RfL ping group.\n\ntry-job: rfl","shortMessageHtmlLink":"Auto merge of #125209 - Kobzol:rfl-ci, r=Mark-Simulacrum"}},{"before":"0de24a5177b1d49d6304f76f3ab159faaec134f9","after":"a3167859f2fd8ff2241295469876a2b687280bdc","ref":"refs/heads/master","pushedAt":"2024-06-10T17:39:07.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 #125017 - petrochenkov:upctxt, r=cjgillot\n\nrustc_span: Optimize syntax context updates in spans\n\nBy updating inline contexts in place, without touching span interner, when possible.","shortMessageHtmlLink":"Auto merge of #125017 - petrochenkov:upctxt, r=cjgillot"}},{"before":"804421dff5542c9c7da5c60257b5dbc849719505","after":"75ac3b6331873133c4f7a10f2252afd6f3906c6a","ref":"refs/heads/beta","pushedAt":"2024-06-10T15:29:05.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 #126220 - ferrocene:pa-beta-1.80.0, r=pietroalbini\n\n[beta] Prepare Rust 1.80.0\n\nr? `@ghost`","shortMessageHtmlLink":"Auto merge of #126220 - ferrocene:pa-beta-1.80.0, r=pietroalbini"}},{"before":"06194cadcd0948a7100b46737f61e82b8c00d632","after":"0de24a5177b1d49d6304f76f3ab159faaec134f9","ref":"refs/heads/master","pushedAt":"2024-06-10T13:15:17.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 #126225 - Kobzol:tidy-update-rustc-perf, r=onur-ozkan\n\nUpdate `rustc-perf` submodule before running tidy\n\nSince https://github.com/rust-lang/rust/pull/125465, `tidy` checks `src/tools/rustc-perf`, so we need to have it checked out before running `tidy`.\n\nFixes: https://github.com/rust-lang/rust/issues/126224\n\nr? `@onur-ozkan`","shortMessageHtmlLink":"Auto merge of #126225 - Kobzol:tidy-update-rustc-perf, r=onur-ozkan"}},{"before":"1f1dd652d93d909e80449f63655b165a2210fead","after":"804421dff5542c9c7da5c60257b5dbc849719505","ref":"refs/heads/beta","pushedAt":"2024-06-10T12:47:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pietroalbini","name":"Pietro Albini","path":"/pietroalbini","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2299951?s=80&v=4"},"commit":{"message":"Auto merge of #126134 - matthiaskrgr:rollup-vzlegsc, r=matthiaskrgr\n\nRollup of 11 pull requests\n\nSuccessful merges:\n\n - #124012 (Stabilize `binary_heap_as_slice`)\n - #124214 (Parse unsafe attributes)\n - #125572 (Detect pub structs never constructed and unused associated constants)\n - #125781 (prefer `compile::stream_cargo` for building tools)\n - #126030 (Update `./x fmt` command in library/std/src/sys/pal/windows/c/README.md)\n - #126047 (Simplify the rayon calls in the installer)\n - #126052 (More `rustc_parse` cleanups)\n - #126077 (Revert \"Use the HIR instead of mir_keys for determining whether something will have a MIR body.\")\n - #126089 (Stabilize Option::take_if)\n - #126112 (Clean up source root in run-make tests)\n - #126119 (Improve docs for using custom paths with `--emit`)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126134 - matthiaskrgr:rollup-vzlegsc, r=matthiaskrgr"}},{"before":"7bb6510fc1899b008837a376a7fdf31b341cc1bb","after":"129f3b9964af4d4a709d1383930ade12dfe7c081","ref":"refs/heads/stable","pushedAt":"2024-06-10T10:55:21.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 #126219 - ferrocene:pa-stable-1.79.0, r=pietroalbini\n\n[stable] Prepare Rust 1.79.0\n\nr? `@ghost`","shortMessageHtmlLink":"Auto merge of #126219 - ferrocene:pa-stable-1.79.0, r=pietroalbini"}},{"before":"d2fb97fceccb7b7d71c40cc2d3c9b376fd2883aa","after":"06194cadcd0948a7100b46737f61e82b8c00d632","ref":"refs/heads/master","pushedAt":"2024-06-10T08:27:46.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 #126206 - Kobzol:disable-libstdc++-version-check, r=Mark-Simulacrum\n\nRemove libstdc++ version check error\n\nThis keeps the error message from https://github.com/rust-lang/rust/pull/125411, but removes the `exit(1)` call.\n\nThis PR is mostly a hotfix to unblock bootstrap benchmarks in rustc-perf.\n\nHowever, I think that it might be better to just print a warning, in general. If the ABI version does not match, the build might or might not work locally (as we can see on rustc-perf, where it works even if the reported ABI is 7).\n\nIf it does not work (and **if** we can always recognize this during the LLVM wrapper build, instead of having some silent miscompilations), then the user will have to update their libstdc++ anyway, the error does not help them out on its own. So it should be enough to just provide a better error message, without blocking the build.\n\nBut I'm not adamant on that, I just want to unblock bootstrap benchmarks until we can find a way to update libstdc++ on the collector machine.\n\nCC `@onur-ozkan`\n\nr? `@Mark-Simulacrum`","shortMessageHtmlLink":"Auto merge of #126206 - Kobzol:disable-libstdc++-version-check, r=Mar…"}},{"before":"7bb6510fc1899b008837a376a7fdf31b341cc1bb","after":"1f1dd652d93d909e80449f63655b165a2210fead","ref":"refs/heads/beta","pushedAt":"2024-06-10T08:15:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"promote-release[bot]","name":null,"path":"/apps/promote-release","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/217112?s=80&v=4"},"commit":{"message":"Auto merge of #3655 - RalfJung:simd-bitmask, r=RalfJung\n\nportable-simd: add test for non-power-of-2 bitmask\n\n`@calebzulawski` is that the intended behavior? Specifically for arrays, the bitmask `[1, 0, 0, 1, 0, 0, 1, 0, 1, 0]` becomes\n- `[0b01001001, 0b01]` on little endian\n- `[0b10010010, 0b10]` on big endian","shortMessageHtmlLink":"Auto merge of #3655 - RalfJung:simd-bitmask, r=RalfJung"}},{"before":"9b00956e56009bab2aa15d7bff10916599e3d6d6","after":"7bb6510fc1899b008837a376a7fdf31b341cc1bb","ref":"refs/heads/stable","pushedAt":"2024-06-10T08:15:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"promote-release[bot]","name":null,"path":"/apps/promote-release","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/217112?s=80&v=4"},"commit":{"message":"Auto merge of #126093 - cuviper:beta-next, r=cuviper\n\n[beta] backports\n\n- Fix insufficient logic when searching for the underlying allocation #124761\n- Handle field projections like slice indexing in invalid_reference_casting #124908\n- Handle Deref expressions in invalid_reference_casting #124978\n- Fix ICE in non-operand `aggregate_raw_ptr` instrinsic codegen #125184\n- Wrap Context.ext in AssertUnwindSafe #125392\n- Revert problematic opaque type change #125489\n- ast: Revert a breaking attribute visiting order change #125734\n- Update to LLVM 18.1.7 #126061\n- Revert \"Disallow ambiguous attributes on expressions\" on beta #126102 / #126101\n- Silence double-symlink errors while building solaris toolchain #126011\n\nr? cuviper","shortMessageHtmlLink":"Auto merge of #126093 - cuviper:beta-next, r=cuviper"}},{"before":"6d94a8727522e21c4309deb7034f5093531a6a76","after":"d2fb97fceccb7b7d71c40cc2d3c9b376fd2883aa","ref":"refs/heads/master","pushedAt":"2024-06-10T04:34:39.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 #126153 - onur-ozkan:fix-rustdoc-issue-with-ci-rustc, r=Mark-Simulacrum\n\nresolve rustdoc incompatibility with `rust.download-rustc=true` + `rust.channel= beta/stable`\n\nPreviously, we were unable to use `rust.download-rustc` with the beta or stable\nchannel settings through `rust.channel` due to breaking rustdoc UI tests.\nThis was because when using a precompiled nightly compiler from CI, we must use the\nchannel of precompiled compiler and ignore `rust.channel` from the configuration.\n\nThis change addresses that issue in `Builder::doc_rust_lang_org_channel` and allows rustdoc\nUI tests to work with the precompiled compiler even if the channel specified in config.toml is\n\"beta\" or \"stable\".\n\nBlocker for https://github.com/rust-lang/rust/pull/122709","shortMessageHtmlLink":"Auto merge of #126153 - onur-ozkan:fix-rustdoc-issue-with-ci-rustc, r…"}},{"before":"a70b2ae57713ed0e7411c059d582ab382fc4166a","after":"6d94a8727522e21c4309deb7034f5093531a6a76","ref":"refs/heads/master","pushedAt":"2024-06-10T02:26:38.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 #107099 - edward-shen:edward-shen/rustdoc-remap-path-prefix, r=GuillaumeGomez\n\nrustdoc: Add support for --remap-path-prefix\n\nAdds `--remap-path-prefix` as an unstable option. This is implemented to mimic the behavior of `rustc`'s `--remap-path-prefix`.\n\nThis flag similarly takes in two paths, a prefix to replace and a replacement string.\n\nThis is useful for build tools (e.g. Buck) other than cargo that can run doc tests.\n\ncc: `@dtolnay`","shortMessageHtmlLink":"Auto merge of #107099 - edward-shen:edward-shen/rustdoc-remap-path-pr…"}},{"before":"503dfcf4e03089cf0c06d10fc69b5477a2f766ef","after":"a70b2ae57713ed0e7411c059d582ab382fc4166a","ref":"refs/heads/master","pushedAt":"2024-06-09T23:16:09.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 #126205 - jieyouxu:rollup-s64z5ng, r=jieyouxu\n\nRollup of 4 pull requests\n\nSuccessful merges:\n\n - #126172 (Weekly `cargo update`)\n - #126176 (rustdoc-search: use lowercase, non-normalized name for type search)\n - #126190 (Autolabel run-make tests, remind to update tracking issue)\n - #126194 (Migrate more things to `WinError`)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126205 - jieyouxu:rollup-s64z5ng, r=jieyouxu"}},{"before":"65d1a73aabc03c7f94633bf00eee1b5548c28c14","after":"503dfcf4e03089cf0c06d10fc69b5477a2f766ef","ref":"refs/heads/master","pushedAt":"2024-06-09T21:01:59.000Z","pushType":"push","commitsCount":16,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #126202 - jieyouxu:rollup-2ixnizz, r=jieyouxu\n\nRollup of 6 pull requests\n\nSuccessful merges:\n\n - #125041 (Enable GVN for `AggregateKind::RawPtr`)\n - #125253 (Add `FRAC_1_SQRT_2PI` constant to f16/f32/f64/f128)\n - #125465 (bootstrap: vendor crates required by opt-dist to collect profiles )\n - #125470 (Add release notes for 1.79.0)\n - #125963 (Remove hard-coded hashes from codegen tests)\n - #126188 (Fix documentation for `impl_common_helpers` in `run-make-support`)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of #126202 - jieyouxu:rollup-2ixnizz, r=jieyouxu"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEY5-TaAA","startCursor":null,"endCursor":null}},"title":"Activity · rust-lang/rust"}