Hashmap section on const/static construction should mention LazyLock as a way to resolve problems mentioned.
#137566
Assignees
Labels
A-collections
Area: `std::collections`
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
Comments
burtonageo
added
the
A-docs
rustbot
added
the
needs-triage
lolbinarycat
added
A-collections
Noratrieb
added
E-easy
|
@rustbot claim |
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 14, 2025
Rollup merge of rust-lang#137870 - karolzwolak:lazylock-const-hashmaps-137566, r=cuviper Improve HashMap docs for const and static initializers Closes rust-lang#137566. I clarified the HashMap usage in const and static initializers. I also added examples of how to construct such HashMaps wrapped in LazyLock.
github-actions bot
pushed a commit
to model-checking/verify-rust-std
that referenced
this issue
Mar 19, 2025
…s-137566, r=cuviper Improve HashMap docs for const and static initializers Closes rust-lang#137566. I clarified the HashMap usage in const and static initializers. I also added examples of how to construct such HashMaps wrapped in LazyLock.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Location
https://doc.rust-lang.org/stable/std/collections/struct.HashMap.html#usage-in-const-and-static
Summary
In the documentation for HashMap, the section on using it in a
static/constcontext mentions that a const seed should be used. However, using aLazyLock<>to wrap theHashMapallows it to be constructed with a random seed, which resolves the main problem highlighted at the end of the paragraph.LazyLockhas been stabilized as of rust 1.80The text was updated successfully, but these errors were encountered: