itchyny
itchyny
No explanation on not using the release tarballs, so closing.
Yeah, defining range/2 by jq-coded (#1960) was rejected previously due to an objection about performance and type validation.
@kirkoman Could you rebase the changes? The dev manual should be updated.
Should this flag block use of [env](https://jqlang.github.io/jq/manual/#$env-env)?
The `input`, `inputs` are safe, but I think wader is talking about `input_filename` and `input_line_number`.
Sorry for waiting, but I think we need more discussion on this topic. Using `seccomp(2)` could be better, or simple `chroot(2)` might be enough. Yes, platform-independent block like this PR...
Any example how useful it is? I'm not sure how common this conversion is, and I'm afraid using this tends to make query less readable.
How about making `length` work on booleans? I've never heard of length of booleans, but neither of length of null, which already works.
Invoke with `-n` option not to read the first value as query input; `jq -n 'inputs'`.