diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2025-08-05 03:51:38 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-05 03:51:38 +0200 |
| commit | 1724af9f1e91cc5dc337645544550ec7df5a5fd5 (patch) | |
| tree | c0c535d994a18bf19cc92518135c7899c12efd14 /compiler/rustc_interface/src/errors.rs | |
| parent | db7ac64997bcf1c5b6e86a403725f7b0c0360fda (diff) | |
| parent | 96adb7df9628ae2f495dbafde387dda0152e5fb8 (diff) | |
| download | rust-1724af9f1e91cc5dc337645544550ec7df5a5fd5.tar.gz rust-1724af9f1e91cc5dc337645544550ec7df5a5fd5.zip | |
Rollup merge of #144872 - connortsui20:once-poison-docs, r=Amanieu
Document Poisoning in `LazyCell` and `LazyLock` Currently, there is no documentation of poisoning behavior in either `LazyCell` or `LazyLock`, even though both of them can be observed as poisoned by users. `LazyCell` [plagyround example](https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=9cf38b8dc56db100848f54085c2c697d) `LazyLock` [playground example](https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=f1cd6f9fe16636e347ebb695a0ce30c0) # Open Questions - [x] Is it worth making the implementation of `LazyLock` more complicated to ensure that the the panic message is `"LazyLock instance has previously been poisoned"` instead of `"Once instance has previously been poisoned"`? See the `LazyLock` playground link above for more context. - [x] Does it make sense to move `LazyLock` into the `poison` module? It is certainly a poison-able type, but at the same time it is slightly different from the 4 other types currently in the `poison` module in that it is unrecoverable. I think this is more of a libs-api question. ``@rustbot`` label +T-libs-api Please let me know if these open questions deserve a separate issue / PR!
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions