-
-
Notifications
You must be signed in to change notification settings - Fork 34
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.
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
Clarify that calling MatchSelectorKeys always returns a list #828
Conversation
The description of this PR and the text seem different? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion for the fallback handling.
@@ -549,6 +549,10 @@ The returned list MAY be empty. | |||
The most-preferred key is first, | |||
with each successive key appearing in order by decreasing preference. | |||
|
|||
If calling MatchSelectorKeys encounters any error, | |||
a _Bad Selector_ error is emitted | |||
and an empty list is returned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and an empty list is returned. | |
and an empty list is returned. | |
The fallback representation of such a _message_ is | |
the _fallback value_ for the _message_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That correction does not match what the algorithm results in. If we get an empty list here, we end up selecting the *
variant.
Follow-up to #816 (comment), as it was not previously clear that MatchSelectorKeys never fails.