https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2023-08-22T13:10:56+00:00 2023-08-22T13:10:56+00:00 kadiwa kalle.wachsmuth@gmail.com 2023-08-22T12:43:53+00:00 urn:sha1:265c1b5d5025a1cb3bdc26b99f35317079a55c36 2023-07-27T21:07:08+00:00 Josh Stone jistone@redhat.com 2023-07-27T21:07:08+00:00 urn:sha1:190ded84434f435b9626a07278b9ed0e7603bd11 2023-05-23T14:54:34+00:00 Pietro Albini pietro.albini@ferrous-systems.com 2023-05-23T13:27:05+00:00 urn:sha1:292bc548c882686f40886934f2055f3440a87eca The attribute is not emitted on targets without unwinding tables. 2023-05-23T14:54:33+00:00 Pietro Albini pietro.albini@ferrous-systems.com 2023-05-23T13:26:31+00:00 urn:sha1:dc1ed9ddd7d15dfe75453b68bc1da8ae32dbe1f7 The attribute is injected into most items when static relocation is enabled in a target. 2023-01-17T07:14:35+00:00 Nilstrieb 48135649+Nilstrieb@users.noreply.github.com 2022-12-30T14:55:05+00:00 urn:sha1:645c0fddd2e0446cc0e6eecd8a78de4b5ab5a967 Previously, it was only put on scalars with range validity invariants like bool, was uninit was obviously invalid for those. Since then, we have normatively declared all uninit primitives to be undefined behavior and can therefore put `noundef` on them. The remaining concern was the `mem::uninitialized` function, which cause quite a lot of UB in the older parts of the ecosystem. This function now doesn't return uninit values anymore, making users of it safe from this change. The only real sources of UB where people could encounter uninit primitives are `MaybeUninit::uninit().assume_init()`, which has always be clear in the docs about being UB and from heap allocations (like reading from the spare capacity of a vec. This is hopefully rare enough to not break anything. 2023-01-11T09:32:08+00:00 Albert Larsan 74931857+albertlarsan68@users.noreply.github.com 2023-01-05T08:13:28+00:00 urn:sha1:cf2dff2b1e3fa55fa5415d524200070d0d7aacfe