rust/library/std/src/sys/pal, branch 1.83.0

Rollup merge of #130962 - nyurik:opts-libs, r=cuviper

2024-10-12T03:57:44+00:00

Migrate lib's `&Option` into `Option<&T>` Trying out my new lint https://github.com/rust-lang/rust-clippy/pull/13336 - according to the [video](https://www.youtube.com/watch?v=6c7pZYP_iIE), this could lead to some performance and memory optimizations. Basic thoughts expressed in the video that seem to make sense: * `&Option` in an API breaks encapsulation: * caller must own T and move it into an Option to call with it * if returned, the owner must store it as Option internally in order to return it * Performance is subject to compiler optimization, but at the basics, `&Option` points to memory that has `presence` flag + value, whereas `Option<&T>` by specification is always optimized to a single pointer.

Decouple WASIp2 sockets from WasiFd

2024-10-09T12:39:28+00:00

Update library/std/src/sys/pal/unix/process/process_vxworks.rs

2024-10-09T03:26:30+00:00

Co-authored-by: Josh Stone

fix ref in process_vxworks.rs

2024-10-09T03:26:30+00:00

Update library/std/src/sys/pal/unix/process/process_unix.rs

2024-10-09T03:26:30+00:00

Co-authored-by: Josh Stone

Change a few `&Option` into `Option<&T>`

2024-10-09T03:26:29+00:00

Android: Debug assertion after setting thread name

2024-10-05T18:29:40+00:00

std: make `thread::current` available in all `thread_local!` destructors

2024-10-02T16:04:21+00:00

Hook up std::net to wasi-libc on wasm32-wasip2 target

2024-09-29T02:48:12+00:00

Use `&raw` in the standard library

2024-09-26T00:03:20+00:00

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.