@@ -24,9 +24,22 @@ or _Message Function Errors_ in _expressions_ that are not otherwise used by the
2424such as _ placeholders_ in unselected _ patterns_
2525or _ declarations_ that are never referenced during _ formatting_ .
2626
27- In all cases, when encountering a runtime error,
28- a message formatter MUST provide some representation of the message.
29- An informative error or errors MUST also be separately provided.
27+ When formatting a _ message_ with one or more errors,
28+ an implementation MUST provide a mechanism to discover and identify
29+ at least one of the errors.
30+ The exact form of error signaling is implementation defined.
31+ Some examples include throwing an exception,
32+ returning an error code,
33+ or providing a function or method for enumerating any errors.
34+
35+ For all _ messages_ without _ Syntax Errors_ or _ Data Model Errors_ ,
36+ an implementation MUST enable a user to get a formatted result.
37+ The formatted result might include _ fallback values_
38+ such as when a _ placeholder_ 's _ expression_ produced an error
39+ during formatting.
40+
41+ The two above requirements MAY be fulfilled by a single formatting method,
42+ or separately by more than one such method.
3043
3144When a message contains more than one error,
3245or contains some error which leads to further errors,
0 commit comments