rust/library/core/src/slice/iter, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-02-23T16:11:00+00:00rename sub_ptr 😅2025-02-23T16:11:00+00:00bendnbend.n@outlook.com2025-02-23T13:26:28+00:00urn:sha1:c813d8f3e49aa4c85c9eded426b6507701a2ff94Add real safety comments2025-02-15T06:59:19+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-02-15T06:59:19+00:00urn:sha1:7add35831955f8fc5ba08dcdb93921cd8de17841Go back to `Some` instead of transmuting to it.2025-02-15T06:24:27+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-02-14T06:53:35+00:00urn:sha1:39118d6181df1ffef6e4407bbf273542ae5efe3c
This adds a few more statements to `next`, but optimizes better in the loops (saving 2 blocks in `forward_loop`, for example)
Save another BB by using `SubUnchecked` instead of a call to `arith_offset`2025-02-15T06:24:27+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-02-14T06:28:29+00:00urn:sha1:3a62c70051e40fbcfc7e5b9ad60cb9cfc4dddcee
Probably reasonable anyway since it more obviously drops provenance.
Simplify `slice::Iter::next` enough that it inlines2025-02-15T06:24:27+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-02-09T09:57:23+00:00urn:sha1:aede8f5fbff92bd1b257685c2e654a9bdf3a021f`transmute` should also assume non-null pointers2025-02-13T07:01:27+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-02-08T08:14:31+00:00urn:sha1:0cc14b688d274096ee4765a33488874a8d84e361
Previously it only did integer-ABI things, but this way it does data pointers too. That gives more information in general to the backend, and allows slightly simplifying one of the helpers in slice iterators.
Use `&raw` in the standard library2024-09-26T00:03:20+00:00Josh Stonejistone@redhat.com2024-09-26T00:03:20+00:00urn:sha1:f4d9d1a0eaf7e5de8c368ac5af500adf9e06f6e7
Since the stabilization in #127679 has reached stage0, 1.82-beta, we can
start using `&raw` freely, and even the soft-deprecated `ptr::addr_of!`
and `ptr::addr_of_mut!` can stop allowing the unstable feature.
I intentionally did not change any documentation or tests, but the rest
of those macro uses are all now using `&raw const` or `&raw mut` in the
standard library.
Shrink some slice iterator MIR2024-06-20T04:35:37+00:00Scott McMurrayscottmcm@users.noreply.github.com2024-06-17T08:49:09+00:00urn:sha1:eac6b2910a5513a3d395814aa20739cabd388723Convert some iter macros to normal functions2024-04-26T05:16:02+00:00Scott McMurrayscottmcm@users.noreply.github.com2024-04-26T05:16:02+00:00urn:sha1:cd47a0ed086ca89faa64776ff15e118ba6aa27f3
With all the MIR optimization changes that have happened since these were written, let's see if they still actually matter.
Replace `NonZero::<_>::new` with `NonZero::new`.2024-02-15T07:09:42+00:00Markus Reiterme@reitermark.us2024-02-08T22:03:25+00:00urn:sha1:a90cc05233858fcd16c3ca0e0b4320fc5ae09af2