rust/tests/ui/consts/copy-intrinsic.stderr, branch autohttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=auto2025-06-07T11:42:30+00:00const-eval error: always say in which item the error occurred2025-06-07T11:42:30+00:00Ralf Jungpost@ralfj.de2025-06-07T09:32:09+00:00urn:sha1:17946c22b1d7abd2dd990bf6998c8491b534fe62
also adjust the wording a little so that we don't say "the error occurred here" for two different spans
Clarify why we are talking about a failed const eval at a random place2025-06-02T15:37:15+00:00Oli Scherergithub333195615777966@oli-obk.de2025-05-30T14:06:35+00:00urn:sha1:020216c31c1e4f1f56a689df8f04580504354613Use the informative error as the main const eval error message2025-06-02T15:37:15+00:00Oli Scherergithub333195615777966@oli-obk.de2025-05-28T10:29:08+00:00urn:sha1:b331b8b96d86a6433df957a3cc49ed51f3656135make std::intrinsic functions actually be intrinsics2025-05-20T06:09:16+00:00Ralf Jungpost@ralfj.de2025-04-16T12:50:18+00:00urn:sha1:a29756d0853654cc4deb7c9ed899156f0ed19ca6interpret: better error message for out-of-bounds pointer arithmetic and accesses2025-04-30T16:45:41+00:00Ralf Jungpost@ralfj.de2025-04-30T14:52:25+00:00urn:sha1:00f25a8e1cf7d749946a6a9fb7327bf4710c931fremove support for extern-block const intrinsics2024-11-04T22:27:45+00:00Ralf Jungpost@ralfj.de2024-11-01T21:19:42+00:00urn:sha1:10723c28964d582814ea8e07dbd8fa7367e0eaeeRe-do recursive const stability checks2024-10-25T18:31:40+00:00Ralf Jungpost@ralfj.de2024-10-06T17:59:19+00:00urn:sha1:a0215d8e46aab41219dea0bb1cbaaf97dafe2f89
Fundamentally, we have *three* disjoint categories of functions:
1. const-stable functions
2. private/unstable functions that are meant to be callable from const-stable functions
3. functions that can make use of unstable const features
This PR implements the following system:
- `#[rustc_const_stable]` puts functions in the first category. It may only be applied to `#[stable]` functions.
- `#[rustc_const_unstable]` by default puts functions in the third category. The new attribute `#[rustc_const_stable_indirect]` can be added to such a function to move it into the second category.
- `const fn` without a const stability marker are in the second category if they are still unstable. They automatically inherit the feature gate for regular calls, it can now also be used for const-calls.
Also, several holes in recursive const stability checking are being closed.
There's still one potential hole that is hard to avoid, which is when MIR
building automatically inserts calls to a particular function in stable
functions -- which happens in the panic machinery. Those need to *not* be
`rustc_const_unstable` (or manually get a `rustc_const_stable_indirect`) to be
sure they follow recursive const stability. But that's a fairly rare and special
case so IMO it's fine.
The net effect of this is that a `#[unstable]` or unmarked function can be
constified simply by marking it as `const fn`, and it will then be
const-callable from stable `const fn` and subject to recursive const stability
requirements. If it is publicly reachable (which implies it cannot be unmarked),
it will be const-unstable under the same feature gate. Only if the function ever
becomes `#[stable]` does it need a `#[rustc_const_unstable]` or
`#[rustc_const_stable]` marker to decide if this should also imply
const-stability.
Adding `#[rustc_const_unstable]` is only needed for (a) functions that need to
use unstable const lang features (including intrinsics), or (b) `#[stable]`
functions that are not yet intended to be const-stable. Adding
`#[rustc_const_stable]` is only needed for functions that are actually meant to
be directly callable from stable const code. `#[rustc_const_stable_indirect]` is
used to mark intrinsics as const-callable and for `#[rustc_const_unstable]`
functions that are actually called from other, exposed-on-stable `const fn`. No
other attributes are required.
stabilize const_mut_refs2024-09-15T07:51:32+00:00Ralf Jungpost@ralfj.de2024-08-17T12:19:34+00:00urn:sha1:3175cc2814dfa8a5201fdb165d67cc44300a77f4improve dangling/oob errors and make them more uniform2024-07-27T19:12:54+00:00Ralf Jungpost@ralfj.de2024-07-27T16:09:50+00:00urn:sha1:f8ebe8d783e20c44508fab32b708f1b9d9a4bf13offset, offset_from: allow zero-byte offset on arbitrary pointers2024-05-13T05:59:16+00:00Ralf Jungpost@ralfj.de2024-05-09T10:35:11+00:00urn:sha1:5c33a5690de89587b645fb0e7b657fe545e4d0e8