Skip to content

Commit

Permalink
Define "option resolution" and require order to be insignificant (#920)
Browse files Browse the repository at this point in the history
This addresses concerns raised in #903 

- define `option resolution` as a term
- require that option order is not significant

I was tempted to define the term `resolved options`, but held back.
  • Loading branch information
aphillips authored Oct 28, 2024
1 parent 530e63b commit db82a8b
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion spec/formatting.md
Original file line number Diff line number Diff line change
Expand Up @@ -333,7 +333,15 @@ Implementation-defined _functions_ SHOULD use an implementation-defined _namespa
#### Option Resolution
The result of resolving _option_ values is an unordered mapping of string identifiers to values.
**_<dfn>Option resolution</dfn>_** is the process of computing the _options_
for a given _expression_.
_Option resolution_ results in a mapping of string _identifiers_ to _values_.
The order of _options_ MUST NOT be significant.
> For example, the following _message_ treats both both placeholders identically:
> ```
> {$x :function option1=foo option2=bar} {$x :function option2=bar option1=foo}
> ```
For each _option_:
Expand Down

0 comments on commit db82a8b

Please sign in to comment.