https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.88.0 2025-05-01T19:05:02+00:00 2025-05-01T19:05:02+00:00 Boxy rust@boxyuwu.dev 2025-05-01T12:26:23+00:00 urn:sha1:238d113b0726b9734ec42737cbc461d08520bf35 2025-04-30T14:42:33+00:00 Romain Perier romain.perier@gmail.com 2025-04-30T14:20:32+00:00 urn:sha1:ea7af1803fc0923ae68d7ffc440ca52c7e1e65d3 This commit does the following: - Replaces use of rustc_type_ir by rustc_middle - Removes the rustc_type_ir dependency - The DelayedSet type is exposed by rustc_middle so everything can be accessed through rustc_middle in a coherent manner. 2025-04-28T17:22:11+00:00 bors bors@rust-lang.org 2025-04-28T17:22:11+00:00 urn:sha1:25cdf1f67463c9365d8d83778c933ec7480e940b Rollup of 7 pull requests Successful merges: - #140056 (Fix a wrong error message in 2024 edition) - #140220 (Fix detection of main function if there are expressions around it) - #140249 (Remove `weak` alias terminology) - #140316 (Introduce `BoxMarker` to improve pretty-printing correctness) - #140347 (ci: clean more disk space in codebuild) - #140349 (ci: use aws codebuild for the `dist-x86_64-linux` job) - #140379 (rustc-dev-guide subtree update) r? `@ghost` `@rustbot` modify labels: rollup 2025-04-28T11:30:45+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-04-28T11:30:45+00:00 urn:sha1:7843686ffeafbabdfeacc4731e43b7b239268f62 Remove `weak` alias terminology I find the "weak" alias terminology to be quite confusing. It implies the existence of "strong" aliases (which do not exist) and I'm not really sure what about weak aliases is "weak". I much prefer "free alias" as the term. I think it's much more obvious what it means as "free function" is a well defined term that already exists in rust. It's also a little confusing given "weak alias" is already a term in linker/codegen spaces which are part of the compiler too. Though I'm not particularly worried about that as it's usually very obvious if you're talking about the type system or not lol. I'm also currently trying to write documentation about aliases and it's somewhat awkward/confusing to be talking about *weak* aliases, when I'm not really sure what the basis for that as the term actually *is*. I would also be happy to just find out there's a nice meaning behind calling them "weak" aliases :-) r? `@oli-obk` maybe we want a types MCP to decide on a specific naming here? or maybe we think its just too late to go back on this naming decision ^^' 2025-04-28T09:23:13+00:00 Andrew Zhogin andrew.zhogin@gmail.com 2024-08-26T13:45:15+00:00 urn:sha1:c366756a8537ef998d32c1ef57098d5aae7ca92f 2025-04-26T02:05:31+00:00 lcnr rust@lcnr.de 2025-04-26T01:54:09+00:00 urn:sha1:855035b03860b00b6f8239e31beec0d3cb882db6 2025-04-24T10:59:20+00:00 Boxy rust@boxyuwu.dev 2025-04-24T10:31:33+00:00 urn:sha1:bdfeb8f36bb2716eb8f5aca32ba4f81563a6818b 2025-04-24T09:40:46+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-24T09:40:46+00:00 urn:sha1:1553cfa4e6ac95afd5faa14aae94aac0138e4305 Remove comment about handling non-global where bounds with corresponding projection This comment is no longer relevant since we only assemble rigid projections if no param-env candidates hold. Also remove a stray comment from the old solver. r? lcnr 2025-04-23T18:36:37+00:00 Michael Goulet michael@errs.io 2025-04-23T17:02:43+00:00 urn:sha1:1162f42b86a5a67211a7e45b40729801a61cdd6e 2025-04-23T15:09:25+00:00 Michael Goulet michael@errs.io 2025-04-22T23:31:22+00:00 urn:sha1:f943f73db4791d64ff83d72986da8d6250c42933