https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=stable 2025-06-14T09:57:06+00:00 2025-06-14T09:57:06+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2024-12-06T09:06:51+00:00 urn:sha1:3e944fa3917a58e30d970d2cce42c14c5edf390b 2025-06-04T06:38:50+00:00 Ralf Jung post@ralfj.de 2025-06-01T08:42:37+00:00 urn:sha1:f01bbfc5e78b4abefe5b386dcf8e83ced4cbe664 2025-06-03T17:03:44+00:00 Jubilee Young workingjubilee@gmail.com 2025-05-21T20:50:21+00:00 urn:sha1:72ecde27ff3f0c02a738acd45d94d5588cb446cc 2025-04-24T06:12:58+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-24T06:12:58+00:00 urn:sha1:32b2428c8b6c7f9c163c313db9826ebf0d08ea6d Don't warn about `v128` in wasm ABI transition The `-Zwasm-c-abi=spec` mode of `extern "C"` does not actually change the meaning of `v128` meaning that the FCW lint firing is a false positive. cc https://github.com/rust-lang/rust/issues/138762#issuecomment-2801709483 2025-04-22T22:11:23+00:00 Alex Crichton alex@alexcrichton.com 2025-04-14T14:41:27+00:00 urn:sha1:19e44d463bf671f6ec1b02b32837ad54dd5d626f This has other warnings if necessary and doesn't need extra warnings from this FCW. cc #138762 2025-04-20T09:34:56+00:00 Ralf Jung post@ralfj.de 2025-04-03T08:59:49+00:00 urn:sha1:b5f5f62a8b5890be2fde163ba3f2284f023126ad 2025-04-17T19:53:24+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-17T19:53:24+00:00 urn:sha1:8b7a2897c87b875ef55d403efccac4b0cc354e16 Ignore zero-sized types in wasm future-compat warning This commit fixes a false positive of the warning triggered for #138762 and the fix is to codify that zero-sized types are "safe" in both the old and new ABIs. 2025-04-17T14:42:55+00:00 Alex Crichton alex@alexcrichton.com 2025-04-07T19:35:02+00:00 urn:sha1:f9091e24a0af713378ee705c86689c1435d0b157 This commit fixes a false positive of the warning triggered for #138762 and the fix is to codify that zero-sized types are "safe" in both the old and new ABIs. 2025-04-14T06:13:04+00:00 Nicholas Nethercote n.nethercote@gmail.com 2025-04-10T20:28:59+00:00 urn:sha1:ce2aa97cd647bdfcb5859489d93526622bb388a0 `hir::AssocItem` currently has a boolean `fn_has_self_parameter` field, which is misplaced, because it's only relevant for associated fns, not for associated consts or types. This commit moves it (and renames it) to the `AssocKind::Fn` variant, where it belongs. This requires introducing a new C-style enum, `AssocTag`, which is like `AssocKind` but without the fields. This is because `AssocKind` values are passed to various functions like `find_by_ident_and_kind` to indicate what kind of associated item should be searched for, and having to specify `has_self` isn't relevant there. New methods: - Predicates `AssocItem::is_fn` and `AssocItem::is_method`. - `AssocItem::as_tag` which converts `AssocItem::kind` to `AssocTag`. Removed `find_by_name_and_kinds`, which is unused. `AssocItem::descr` can now distinguish between methods and associated functions, which slightly improves some error messages. 2025-04-10T15:27:14+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-10T15:27:14+00:00 urn:sha1:79f357e63d078512e5d8bb8ad7ff5f0b7e52b473 Rename some `name` variables as `ident`. It bugs me when variables of type `Ident` are called `name`. It leads to silly things like `name.name`. `Ident` variables should be called `ident`, and `name` should be used for variables of type `Symbol`. This commit improves things by by doing `s/name/ident/` on a bunch of `Ident` variables. Not all of them, but a decent chunk. r? `@fee1-dead`