Skip to content

Commit

Permalink
Avoid presumptive use of "always" (#776)
Browse files Browse the repository at this point in the history
* Avoid presumptive use of "always"

* Explain the example Unsupported Expression error
  • Loading branch information
gibson042 authored Apr 29, 2024
1 parent ed6b1da commit 5efe659
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions spec/errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,8 @@ syntax reserved for future standardization,
or for private implementation use that is not supported by the current implementation.
> For example, attempting to format this message
> would always result in an _Unsupported Expression_ error:
> would result in an _Unsupported Expression_ error
> because it includes a _reserved annotation_.
>
> ```
> The value is {!horse}.
Expand Down Expand Up @@ -274,7 +275,7 @@ for that specific _function_.
An **_<dfn>Unsupported Statement</dfn>_** error occurs when a message includes a _reserved statement_.
> For example, attempting to format this message
> would always result in an _Unsupported Statement_ error:
> would result in an _Unsupported Statement_ error:
>
> ```
> .some {|horse|}
Expand Down

0 comments on commit 5efe659

Please sign in to comment.