You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsC-bugCategory: This is a bug.T-libsRelevant to the library team, which will review and decide on the PR/issue.
The documentation comments of the three try_reserve_exact methods stabilized today in 1.57.0 (in Vec, String, and VecDeque) all have the same note as the corresponding aborting method reserve_exact:
Prefer reserve if future insertions are expected.
For the fallible try_reserve_exact methods, should that say try_reserve rather than reserve?
The text was updated successfully, but these errors were encountered:
inquisitivecrystal
added
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
labels
Dec 3, 2021
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsC-bugCategory: This is a bug.T-libsRelevant to the library team, which will review and decide on the PR/issue.
The documentation comments of the three
try_reserve_exact
methods stabilized today in 1.57.0 (inVec
,String
, andVecDeque
) all have the same note as the corresponding aborting methodreserve_exact
:For the fallible
try_reserve_exact
methods, should that saytry_reserve
rather thanreserve
?The text was updated successfully, but these errors were encountered: