pkoppstein

@itchyny - The point is that whereas "-1" is a JSON number; "- 1" is not. (It's not even JSON, as `jq .` and `gojq .` both attest.) For jq...

> We could fix this ... Since I opened this issue, I should add that I think it's relatively unimportant, a view that is perhaps supported by the fact that...

@nicowilliams wrote: > My strong preference is that we add no command-line options for input/output formats That would be fine except for the question of "legacy" extensions (`00` for 0,...

@flipmcf - Yes, bloat causes significant costs in multiple respects (not least the problems associated with complexity in general and feature interaction in particular), especially for volunteer projects such as...

That sentence was evidently not intended to be taken out of context, the context being the construction of filters to form a pipeline, not the construction of LHS expressions. Since...

@nicowilliams wrote: > This construction has the same problem if what follows .a | .b were an assignment. In the context in which it appears, it seems to me that...

I have no objections to not supporting negative indices. There is currently no named def for .[length-2] but if there were, it would work, so I don’t see any issue...

@nicowilliams wrote: > please check if you can make pick/1 use a path normalization function ... I will do so, but for 1.7, I am inclined to think it would...

@wader wrote: > Accidentally added line? It was added by `make jq.1.prebuilt` (!!!) I removed it manually. Thanks.

To be clear, the point is that the current processing of `nan123` entails silent loss of data (or at least silent loss of presumptive data) and thus differs from the...