Bug fix: Optional sequences shouldn't be defaulted to null #539
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MLArgMinMaxOptions and MLReduceOptions have an 'axes' member that the IDL declares as defaulting to null. They have type sequence which is not nullable. The intent is that these are optional members with default behavior if not present, which is handled in the algorithm already.
If the desire is to be able to explicitly pass null, the IDL fix would be to make the type nullable:
sequence<unsigned long>? axes = null;
but that's inconsistent with the rest of the spec and not the convention for optional dictionary members.Preview | Diff