<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/library/std, branch auto</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=auto</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=auto'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-10-04T10:31:27+00:00</updated>
<entry>
<title>Rollup merge of #147190 - joboet:sys-net-cleanup, r=hkBst,tgross35</title>
<updated>2025-10-04T10:31:27+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-10-04T10:31:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=97554669dd4cd5f4a425e515e0f5632955824005'/>
<id>urn:sha1:97554669dd4cd5f4a425e515e0f5632955824005</id>
<content type='text'>
std: `sys::net` cleanups

This PR contains three improvements to the socket-based networking implementation (aa1263e7684341a73b600eaf0bbc70067e196243 is just to add the now missing `unsafe`). Best reviewed commit-by-commit.
</content>
</entry>
<entry>
<title>Rollup merge of #146451 - DimitriiTrater:atan2_correctness_docs, r=tgross35</title>
<updated>2025-10-04T10:31:25+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-10-04T10:31:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=eb8e240de97e27807e1079239024c888968e2453'/>
<id>urn:sha1:eb8e240de97e27807e1079239024c888968e2453</id>
<content type='text'>
Fix atan2 inaccuracy in documentation

Fixes rust-lang/rust#136275
</content>
</entry>
<entry>
<title>Document fully-qualified syntax in `as`' keyword doc</title>
<updated>2025-10-03T14:31:55+00:00</updated>
<author>
<name>Fletcher Porter</name>
<email>me@fletcherporter.com</email>
</author>
<published>2025-06-18T12:04:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=1485e7887b6407ce6326e044d9b3983364db52ad'/>
<id>urn:sha1:1485e7887b6407ce6326e044d9b3983364db52ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #146281 - Jules-Bertholet:static-align-thread-local, r=Mark-Simulacrum</title>
<updated>2025-10-02T08:27:48+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-10-02T08:27:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=92aac1bdf61642cfc99498ca86e663cf53d2039e'/>
<id>urn:sha1:92aac1bdf61642cfc99498ca86e663cf53d2039e</id>
<content type='text'>
Support `#[rustc_align_static]` inside `thread_local!`

Tracking issue: rust-lang/rust#146177

```rust
thread_local! {
    #[rustc_align_static(64)]
    static SO_ALIGNED: u64 = const { 0 };
}
```

This increases the amount of recursion the macro performs (once per attribute in addition to the previous once per item), making it easier to hit the recursion limit. I’ve added workarounds to limit the impact in the case of long doc comments, but this still needs a crater run just in case.

r? libs

``@rustbot`` label A-attributes A-macros A-thread-locals F-static_align T-libs
</content>
</entry>
<entry>
<title>Fix memory leak in `os` impl</title>
<updated>2025-10-01T16:28:18+00:00</updated>
<author>
<name>Jules Bertholet</name>
<email>julesbertholet@quoi.xyz</email>
</author>
<published>2025-10-01T15:32:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=94f00f4e4a0240bc7b8284c78482e37af252309a'/>
<id>urn:sha1:94f00f4e4a0240bc7b8284c78482e37af252309a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #147213 - ivmarkov:fix-hostname-espidf, r=joboet</title>
<updated>2025-10-01T12:15:03+00:00</updated>
<author>
<name>Stuart Cook</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2025-10-01T12:15:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=06e059d45d53d82654cad67eff3905c0577e36ab'/>
<id>urn:sha1:06e059d45d53d82654cad67eff3905c0577e36ab</id>
<content type='text'>
Fix broken STD build for ESP-IDF

PRs rust-lang/rust#147162 and rust-lang/rust#146937 did [broke](https://github.com/esp-rs/esp-idf-sys/actions/runs/18151791720/job/51663969786) the STD build for `target_os = "espidf"` because that target [does not have neither a `gethostname`, not a `libc::_SC_HOST_NAME_MAX` by default](https://github.com/espressif/esp-idf/issues/14849).

While there is a [3rd party component for this syscall](https://components.espressif.com/components/espressif/sock_utils/versions/0.2.2/readme) in the ESP-IDF component registry, I don't think we should use it, because it does not come with ESP-IDF by default.

Therefore, the one-liner fix just re-routes ESP-IDF into the `unsupported` branch.
</content>
</entry>
<entry>
<title>Fix broken STD build for ESP-IDF</title>
<updated>2025-10-01T08:12:44+00:00</updated>
<author>
<name>ivmarkov</name>
<email>ivan.markov@gmail.com</email>
</author>
<published>2025-10-01T08:12:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b1c212f8502e8e7fcb66da0e8da98db770cb7c02'/>
<id>urn:sha1:b1c212f8502e8e7fcb66da0e8da98db770cb7c02</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Auto merge of #147198 - matthiaskrgr:rollup-b0ryvvu, r=matthiaskrgr</title>
<updated>2025-10-01T04:46:14+00:00</updated>
<author>
<name>bors</name>
<email>bors@rust-lang.org</email>
</author>
<published>2025-10-01T04:46:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=1e1a39441bd11aba541a48ba714d939490fc7b85'/>
<id>urn:sha1:1e1a39441bd11aba541a48ba714d939490fc7b85</id>
<content type='text'>
Rollup of 6 pull requests

Successful merges:

 - rust-lang/rust#143069 (Add fast-path for accessing the current thread id)
 - rust-lang/rust#146518 (Improve the documentation around `ZERO_AR_DATE`)
 - rust-lang/rust#146596 (Add a dummy codegen backend)
 - rust-lang/rust#146617 (Don’t suggest foreign `doc(hidden)` types in "the following other types implement trait" diagnostics)
 - rust-lang/rust#146635 (cg_llvm: Stop using `as_c_char_ptr` for coverage-related bindings)
 - rust-lang/rust#147184 (Fix the bevy implied bounds hack for the next solver)

r? `@ghost`
`@rustbot` modify labels: rollup
</content>
</entry>
<entry>
<title>Add fast-path for accessing the current thread id</title>
<updated>2025-09-30T18:51:03+00:00</updated>
<author>
<name>Josh Simmons</name>
<email>josh@nega.tv</email>
</author>
<published>2025-06-26T19:31:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=cbaec31c10c5eff7342e5273360521911fbf7631'/>
<id>urn:sha1:cbaec31c10c5eff7342e5273360521911fbf7631</id>
<content type='text'>
Accessing the thread id is often used in profiling and debugging, as
well as some approaches for sound single-threaded access to data.

Currently the only way to access the thread id is by first obtaining a
handle to the current thread. While this is not exactly slow, it does
require an atomic inc-ref and dec-ref operation, as well as the
injection of `Thread`'s drop code into the caller.

This publicly exposes the existing fast-path for accessing the current
thread id.
</content>
</entry>
<entry>
<title>Rollup merge of #142506 - clarfonthey:path-trailing-sep, r=joboet</title>
<updated>2025-09-30T18:46:44+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-09-30T18:46:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=61b9467af89c18fb2b1e08da1fce2472b2147cc1'/>
<id>urn:sha1:61b9467af89c18fb2b1e08da1fce2472b2147cc1</id>
<content type='text'>
Add `Path::has_trailing_sep` and related methods

Implements rust-lang/libs-team#335.

Tracking issue: rust-lang/rust#142503

Notable differences from ACP:

* `trim_trailing_sep` was added to `Path` since it felt reasonable to ensure that the inverse operation was available.
* Per suggestion of `@kennytm,` added `push_trailing_sep` and `pop_trailing_sep` to `PathBuf` in addition to `set_trailing_sep`.

This also updates some of the docs on various `Path` methods to use the term "trailing separator" instead of "trailing slash" for consistency.
</content>
</entry>
</feed>
