rust/library/std, branch lcnr/rustc-dev-guidehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=lcnr/rustc-dev-guide2025-08-13T05:03:52+00:00Rollup merge of #145325 - clarfonthey:cast-init, r=scottmcm2025-08-13T05:03:52+00:00Jakub Beránekberykubik@gmail.com2025-08-13T05:03:52+00:00urn:sha1:8cb78fe3b63ab1f83d084411cb1f768ce9443a3d
Add `cast_init` and `cast_uninit` methods for pointers
ACP: rust-lang/libs-team#627
Tracking issue: rust-lang/rust#145036
This includes an incredibly low-effort search to find uses that could be switched to using these methods. I only searched for `cast::<\w>` and `cast::<MaybeUninit` because there would otherwise be way too much to look through, and I also didn't modify anything inside submodules/subtrees.
Rollup merge of #145303 - m-ou-se:payload-as-str-doc, r=jhpratt2025-08-13T05:03:50+00:00Jakub Beránekberykubik@gmail.com2025-08-13T05:03:50+00:00urn:sha1:a0ed0889bb246b1bf484d70f9561f1c494049458
Docs: Link to payload_as_str() from payload().
Rollup merge of #144870 - Kivooeo:file_prefix-stabilize, r=tgross352025-08-13T05:03:47+00:00Jakub Beránekberykubik@gmail.com2025-08-13T05:03:47+00:00urn:sha1:ff44871be5b5bd6027c4956eb6d4520e87974c1e
Stabilize `path_file_prefix` feature
This stabilises `Path::file_prefix`, following the FCP in [tracking issue ](https://github.com/rust-lang/rust/issues/86319)
(FCP ended almost a year ago, so if it's needed for proccess we could rerun it)
Closes: https://github.com/rust-lang/rust/issues/86319
Add cast_init and cast_uninit methods for pointers2025-08-12T20:57:56+00:00ltdkusr@ltdk.xyz2025-07-18T03:28:24+00:00urn:sha1:d6945f6d8c15bd692000cd7f8d76d171ae27b8c9Constify SystemTime methods2025-08-12T18:05:47+00:00ltdkusr@ltdk.xyz2025-07-26T22:51:13+00:00urn:sha1:7ce620dd7c6fc3371290b40a1ea28146f0d37031Link to payload_as_str() from payload().2025-08-12T10:50:48+00:00Mara Bosm-ou.se@m-ou.se2025-08-12T10:50:48+00:00urn:sha1:bd44d855f5a2c989b5cc5bef517978c47ddc6779std: sys: pal: uefi: tests: Add systemtime tests2025-08-11T13:40:10+00:00Ayush Singhayush@beagleboard.org2025-05-24T11:36:02+00:00urn:sha1:35906eaabcd8ecf4e92f82630e6fdfbf945f5dc6
Add tests to ensure that extream system times are still representable.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
std: sys: pal: uefi: Overhaul Time2025-08-11T13:28:34+00:00Ayush Singhayush@beagleboard.org2025-04-14T13:25:04+00:00urn:sha1:0ccbe8fc71173bf5d2e348e5b3ed6cb344db913b
Use a time representation with 1900-01-01-00:00:00 at timezone -1440 min as
anchor. This is the earliest time supported in UEFI.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Rollup merge of #145228 - estebank:unnecessary-parens, r=joshtriplett2025-08-11T02:21:10+00:00Stuart CookZalathar@users.noreply.github.com2025-08-11T02:21:10+00:00urn:sha1:fd7d7245594a1c819333cbc4f981ae51ee78930d
Remove unnecessary parentheses in `assert!`s
Rollup merge of #144350 - Ayush1325:uefi-io, r=tgross35,nicholasbishop2025-08-11T02:21:07+00:00Stuart CookZalathar@users.noreply.github.com2025-08-11T02:21:07+00:00urn:sha1:3724e13cc7de90804ff6be508cd47ee8d979feb8
std: sys: io: io_slice: Add UEFI types
UEFI networking APIs do support vectored read/write. While the types for UDP4, UDP6, TCP4 and TCP6 are defined separately, they are essentially the same C struct. So we can map IoSlice and IoSliceMut to have the same binary representation.
Since all UEFI networking types for read/write are DSTs, `IoSlice` and `IoSliceMut` will need to be copied to the end of the transmit/receive structures. So having the same binary representation just allows us to do a single memcpy instead of having to loop and set the DST.
cc ``@nicholasbishop``