diff options
| author | Emanuele Torre <torreemanuele6@gmail.com> | 2023-08-04 22:52:27 +0200 |
|---|---|---|
| committer | Nico Williams <nico@cryptonector.com> | 2023-08-04 17:38:52 -0500 |
| commit | f94a9d463ffb3422861a0da140470dbf5ce76632 (patch) | |
| tree | b63b841402177b23758f6ab54a835d34ae716156 /docs/content | |
| parent | 3b6e7ddd72d6080959a44bdcca068c3a200eb2ef (diff) | |
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.
Diffstat (limited to 'docs/content')
| -rw-r--r-- | docs/content/manual/manual.yml | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/content/manual/manual.yml b/docs/content/manual/manual.yml index 3e2c289d..4028a943 100644 --- a/docs/content/manual/manual.yml +++ b/docs/content/manual/manual.yml @@ -1231,10 +1231,6 @@ sections: given as the argument. Errors can be caught with try/catch; see below. - When the error value is `null`, it produces nothing and works - just like `empty`. So `[null | error]` and `[error(null)]` both - emit `[]`. - examples: - program: 'try error catch .' input: '"error message"' |