On Sat, Nov 23, 2024 at 11:29 PM Miguel Ojeda <ojeda@xxxxxxxxxx> wrote: > > The sibling `build_assert!` is already in the prelude, it makes sense > that a "core"/"language" facility like this is part of the prelude and > users should not be defining their own one (thus there should be no risk > of future name collisions and we would want to be aware of them anyway). > > Thus add `build_error!` into the prelude. > > Signed-off-by: Miguel Ojeda <ojeda@xxxxxxxxxx> Reviewed-by: Alice Ryhl <aliceryhl@xxxxxxxxxx>
