Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update on surprising jq behaviours #215

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Conversation

wader
Copy link
Contributor

@wader wader commented Sep 24, 2024

`[[]] | implode` crash was fixed in 1.7 by jqlang/jq#2646
`[limit(0; 1, 2, 3)]` yielding 1,2 instead of nothing fixed in 1.7 by jqlang/jq#2316
`limit/2` will throw error on negative limit once jqlang/jq#3181 is merged
@wader
Copy link
Contributor Author

wader commented Sep 24, 2024

The NaN compare stuff is a bit weird, maybe would be ok to do a breaking change for that? or could there be some indirect use of NaN compare that would break?

About the performance issues: i think most of them got resolved by jqlang/jq#1834

@01mf02 01mf02 merged commit 8eb4874 into 01mf02:main Oct 11, 2024
1 check passed
@wader wader deleted the less-jq-surprises branch October 11, 2024 07:27
@01mf02
Copy link
Owner

01mf02 commented Oct 11, 2024

Hi @wader, thanks for your PR! Your push motivated me to also remove a few other claims from the README that referred to jq 1.6 and which were not longer true in jq 1.7. So thanks for that. :)

@wader
Copy link
Contributor Author

wader commented Oct 11, 2024

@01mf02 👍 btw i'm slowly reading your "A formal specification of the jq language" paper and hope to get to review your jq docs improvements, been a bit busy with non-jq stuff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants