rfc14: make max key optional in range #475
Merged
+19
−15
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.
Problem: if a non-default
operator
oroperand
are specified, thenmax
would also need to be given, making it more difficult to specify an unbounded range with non-defaultoperator
/operand
combinationsMake the
max
key always optional independent of the the other keys, change to require only theoperator
/operand
keys be specified as a pair, and clarify their default values if unsetRFC14 update to align with flux-framework/flux-core#7130