To clarify the new rich errors proposal, is it pla...
# language-evolution
c
To clarify the new rich errors proposal, is it planned to add new
error data object NotFound
and all
firstOrNotFound
,
firstOfOrNotFound
etc variants? The KEEP mentions how the language will change, but I didn't see anything about the changes to the standard library.
1
m
There's no final decision yet. We've been thinking of a more general version like
firstOrError
or something like that
👍 1
c
Since you replied with another example, I assume it is decided that those functions will exist, what's undecided is only their name?
m
Let me be completely clear: right now we're prototyping the feature and writing a KEEP (two KEEPs, to be precise), so we're in the middle of evaluation and want to understand for ourselves which functions, including their signatures and names, will work best for us. That's why I'm answering in a rather vague way
c
Makes sense, thanks