https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=beta 2025-09-14T18:43:32+00:00 2025-09-14T18:43:32+00:00 Mark Rousskov mark.simulacrum@gmail.com 2025-09-14T14:30:29+00:00 urn:sha1:03265b459f0fb0138c8197377ea3eba279989709 2025-09-13T22:55:20+00:00 Jacob Pratt jacob@jhpratt.dev 2025-09-13T22:55:20+00:00 urn:sha1:da1c27df16075d9ebb28a94cf9b400e89c476233 document `core::ffi::VaArgSafe` tracking issue: https://github.com/rust-lang/rust/issues/44930 A modification of https://github.com/rust-lang/rust/pull/146454, keeping just the documentation changes, but not unsealing the trait. Although conceptually we'd want to unseal the trait, there are many edge cases to supporting arbitrary types. We'd need to exhaustively test that all targets/calling conventions support all types that rust might generate (or generate proper error messages for unsupported cases). At present, many of the `va_arg` implementations assume that the argument is a scalar, and has an alignment of at most 8. That is totally sufficient for an MVP (accepting all of the "standard" C types), but clearly does not cover all rust types. This PR also adds some various other tests for edge cases of c-variadic: - the `#[inline]` attribute in its various forms. At present, LLVM is unable to inline c-variadic functions, but the attribute should still be accepted. `#[rustc_force_inline]` already rejects c-variadic functions. - naked functions should accept and work with a C variable argument list. In the future we'd like to allow more ABIs with naked functions (basically, any ABI for which we accept defining foreign c-variadic functions), but for now only `"C"` and `"C-unwind` are supported - guaranteed tail calls: c-variadic functions cannot be tail-called. That was already rejected, but there was not test for it. r? `@workingjubilee` 2025-09-13T19:04:58+00:00 Folkert de Vries folkert@folkertdev.nl 2025-09-11T21:58:52+00:00 urn:sha1:61a35937861cae48b9ade326f75c00e387e6376a and document `VaList::arg`. 2025-09-12T09:39:31+00:00 Evgenii Zheltonozhskii zheltonozhskiy@gmail.com 2025-09-12T09:39:31+00:00 urn:sha1:ff9b1c1d285821fabe3cbf904fc407d62d95fbdc 2025-09-11T04:06:26+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-11T04:06:26+00:00 urn:sha1:602841dc8c4b9d58d663b4d8a23d91172c45274d core::ptr: deduplicate docs for as_ref, addr, and as_uninit_ref also add INFO.md file explaining the purpose of the ptr/docs dir, and give some pointers (heh) to future maintainers. follow up to rust-lang/rust#142101 part of rust-lang/rust#139190 r? `@workingjubilee` 2025-09-10T16:00:08+00:00 binarycat binarycat@envs.net 2025-06-10T21:35:44+00:00 urn:sha1:d50a80e1d0e655524a3c0dff1f55d7c667314184 also add INFO.md file explaining the purpouse of the ptr/docs dir. 2025-09-10T12:17:37+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-10T12:17:37+00:00 urn:sha1:d0ba5e33ff7e05f6ccd365fe97b822e33beaed6b inclusive `Range`s: change `end` to `last` Tracking issue: rust-lang/rust#125687 ACP: rust-lang/libs-team#511 2025-09-09T04:35:06+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-09T04:35:06+00:00 urn:sha1:fde2ef616d350634f5bfe8664b3acdbd6cdcdd64 simplify the declaration of the legacy integer modules (`std::u32` etc.) This PR removes some duplicated code from the declaration of the legacy integer modules by expanding the macro which is already used to generate `MIN` and `MAX` to now generate the whole module. This would also make the remaining steps listed in rust-lang/rust#68490 such as fully deprecating the modules or placing `#[doc(hidden)]` on them easier. 2025-09-09T04:35:05+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-09T04:35:05+00:00 urn:sha1:915f9ff1602e6c8cf3b5ae29da58b932a91449c6 const-eval: disable pointer fragment support This fixes https://github.com/rust-lang/rust/issues/146291 by disabling pointer fragment support for const-eval. I want to properly fix this eventually, but won't get to it in the next few weeks, so this is an emergency patch to prevent the buggy implementation from landing on stable. The beta cutoff is on Sep 12th so if this PR lands after that, we'll need a backport. 2025-09-09T04:35:04+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-09T04:35:04+00:00 urn:sha1:b543b1444b998cabb5d60823ae73dde8e577d10f mark `format_args_nl!` as `#[doc(hidden)]` The `#[unstable]` attribute of the macro already says: > `format_args_nl` is only for internal language use and is subject to change It does seem plausible to hide it from the `std` docs accordingly. The PR also removes the single usage of the macro outside of `std` as it does not seem like the macro is actually needed there.