Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid presumptive use of "always" #776

Merged
merged 2 commits into from
Apr 29, 2024
Merged

Avoid presumptive use of "always" #776

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7fbd36f
Avoid presumptive use of "always"
gibson042 Apr 24, 2024
7656bec
Explain the example Unsupported Expression error
gibson042 Apr 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions spec/errors.md
View file
Open in desktop
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