-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
A-arrayArea: `[T; N]`Area: `[T; N]`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Description
Provides the common use-case of creating custom fallible arrays in a reliable and unified way. Particularly useful for elements that don't implement Copy, Clone or Default.
Public API
// Unstable
fn try_from_fn<E, F, T, const N: usize>(cb: F) -> Result<[T; N], E>
where
F: FnMut(usize) -> Result<T, E>;
Steps / History
- Implementation (Add 'core::array::from_fn' and 'core::array::try_from_fn' #75644)
- Final comment period
- Stabilization PR
Unresolved Questions
-
Should the callback return indices (Add 'core::array::from_fn' and 'core::array::try_from_fn' #75644 (comment)) ? -
from_fn
andtry_from_fn
are very similar torepeat_with
andtry_repeat_with
(Tracking Issue forcore::array::(try_)repeat(_with)
(featurearray_repeat
) #91613), just that they take unary instead of nullary functions. Anyone considering stabilizing these should think about those, and vice versa.
stepancheg, adriandelgado, MortenLohne and jjpeLukasKalbertodt, jdahlstrom, Kobzol, jeffparsons, scottmcm and 25 morekornelski and adriandelgadog-berthiaume, Shatur, QkiZMR and adriandelgado
Metadata
Metadata
Assignees
Labels
A-arrayArea: `[T; N]`Area: `[T; N]`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.