rust/library/alloc/src/boxed/thin.rs, branch 1.84.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.84.12024-09-26T00:03:20+00:00Use `&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.
Reformat `use` declarations.2024-07-28T22:26:52+00:00Nicholas Nethercoten.nethercote@gmail.com2024-07-28T22:13:50+00:00urn:sha1:84ac80f1921afc243d71fd0caaa4f2838c294102
The previous commit updated `rustfmt.toml` appropriately. This commit is
the outcome of running `x fmt --all` with the new formatting options.
Convert some module-level `//` and `///` comments to `//!`.2024-06-19T23:23:18+00:00Nicholas Nethercoten.nethercote@gmail.com2024-06-19T19:02:12+00:00urn:sha1:09006d6a88019b80f7158f1a5f754a358751d7f1
This makes their intent and expected location clearer. We see some
examples where these comments were not clearly separate from `use`
declarations, which made it hard to understand what the comment is
describing.
Do not allocate for ZST ThinBox attempt 2 (using const_allocate)2024-04-05T18:55:00+00:00Stepan Koltsovstepan.koltsov@gmail.com2024-03-29T03:24:02+00:00urn:sha1:f539134e2098bcc02d5c6228034974c67196adab
There's PR https://github.com/rust-lang/rust/pull/123184
which avoids allocation for ZST ThinBox.
That PR has an issue with unsoundness with misuse of `MaybeUninit`
(see comments in that PR).
This PR is much simpler implementation which does not have this
problem, but it uses `const_allocate` feature.
library: use `addr_of!`2024-02-24T13:02:17+00:00Pavel Grigorenkogrigorenkopv@ya.ru2024-02-24T13:02:17+00:00urn:sha1:ff187a92d84f352670a9a63e8519eac114456d38Rollup merge of #110483 - tleibert:thin-box-try-new, r=dtolnay2024-02-11T22:19:07+00:00Matthias Krügermatthias.krueger@famsik.de2024-02-11T22:19:07+00:00urn:sha1:251a09e151d9a522737913a1c5244e9b6770e476
Create try_new function for ThinBox
The `allocator_api` feature has proven very useful in my work in the FreeBSD kernel. I've found a few places where a `ThinBox` #92791 would be useful, but it must be able to be fallibly allocated for it to be used in the kernel.
This PR proposes a change to add such a constructor for ThinBox.
ACP: https://github.com/rust-lang/libs-team/issues/213
Address ThinBox::try_new PR review2024-02-11T19:28:01+00:00David Tolnaydtolnay@gmail.com2024-02-11T19:15:21+00:00urn:sha1:ea6944a065bdc64855c221f8e2fd969df4d21c6dRemove no-longer-needed `allow(dead_code)` from the standard library2024-01-18T18:14:42+00:00Jake Gouldingjake.goulding@gmail.com2024-01-18T18:14:14+00:00urn:sha1:fb7762b1c51d67a56324b92fd79c85b33d5d1d3b
`repr(transparent)` now silences the lint.
Adjust library tests for unused_tuple_struct_fields -> dead_code2024-01-02T20:34:37+00:00Jake Gouldingjake.goulding@gmail.com2023-12-27T23:03:23+00:00urn:sha1:5772818dc8f4c5a0fec1f5b35b33e85764dcd4f4Address unused tuple struct fields in the standard library2023-11-28T17:00:54+00:00Jake Gouldingjake.goulding@gmail.com2023-11-25T20:45:44+00:00urn:sha1:115eac03bbd2a4b8b301c3bc627bd0f2c1235525