Let error(null) throw null

This patch removes the weird behaviour of jv_invalid_with_msg(jv_null())
that returns jv_invalid() (i.e. empty), instead of a boxed jv_null().

The previous behaviour of  null|error  was obviously unintentional, and
allowing is jv_invalid_with_msg() to return values on which you can't
call jv_invalid_get_msg() is only error prone.
This commit is contained in:
Emanuele Torre authored and Nico Williams committed 2023-08-04 17:38:52 -05:00
1 parent 3b6e7ddd72
commit f94a9d463f
4 files changed
+4 -15

No files matched your search

Generated
-3
View File
@@ -1263,9 +1263,6 @@ jq \'[1,2,empty,3]\'
.SS "error, error(message)"
Produces an error with the input value, or with the message given as the argument\. Errors can be caught with try/catch; see below\.
.
.P
When the error value is \fBnull\fR, it produces nothing and works just like \fBempty\fR\. So \fB[null | error]\fR and \fB[error(null)]\fR both emit \fB[]\fR\.
.
.IP "" 4
.
.nf