Repository navigation
Read the NULL a MEOS argument accepts from the @nullable tag alone - #215
Merged
estebanzimanyi merged 1 commit intoOct 27, 2026
Conversation
A parameter accepts NULL where its @PARAM entry carries the @nullable tag, and shape.nullable lists exactly those parameters. A description naming NULL in prose states nothing: on MobilityDB master such a description describes a value written or another argument. Witness: the dissolved output of a geometry dissolve documented "or NULL where nothing dissolves" is not nullable (test_prose_naming_null_states_nothing); the reader of master answers it nullable. Measured: over MobilityDB master f69b861f64, shape.nullable holds the same 292 parameters of 203 functions as before; the 80 tests of the nullable, outparam and boundargs readers pass. Why: the tag is the one statement of a NULL argument, so a second reading of the prose can only disagree with it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A parameter accepts NULL where its @PARAM entry carries the @nullable tag, and
shape.nullable lists exactly those parameters. A description naming NULL in
prose states nothing: on MobilityDB master such a description describes a
value written or another argument.
Witness: the dissolved output of a geometry dissolve documented "or NULL where
nothing dissolves" is not nullable (test_prose_naming_null_states_nothing);
the reader of master answers it nullable.
Measured: over MobilityDB master f69b861f64, shape.nullable holds the same 292
parameters of 203 functions as before; the 80 tests of the nullable, outparam
and boundargs readers pass.
Why: the tag is the one statement of a NULL argument, so a second reading of
the prose can only disagree with it.