From 0aa15cbb70e8033a9b112603badae7fbdda7fac6 Mon Sep 17 00:00:00 2001
From: Mattias Wadman <mattias.wadman@gmail.com>
Date: Tue, 24 Sep 2024 13:31:00 +0200
Subject: [PATCH] Update on surprising jq behaviours

`[[]] | implode` crash was fixed in 1.7 by https://github.com/jqlang/jq/pull/2646
`[limit(0; 1, 2, 3)]` yielding 1,2 instead of nothing fixed in 1.7 by https://github.com/jqlang/jq/issues/2316
`limit/2` will throw error on negative limit once https://github.com/jqlang/jq/pull/3181 is merged
---
 README.md | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/README.md b/README.md
index cd81f4341..e63099e7e 100644
--- a/README.md
+++ b/README.md
@@ -19,13 +19,6 @@ jaq focuses on three goals:
   <details><summary>Examples of surprising jq behaviour</summary>
 
   * `nan > nan` is false, while `nan < nan` is true.
-  * `[[]] | implode` crashes jq, and this was not fixed at the time of writing despite
-    [being known since five years](https://github.com/jqlang/jq/issues/1160).
-  * The [jq manual] claims that `limit(n; exp)` "extracts up to `n` outputs from `exp`".
-    This holds for values of `n > 1`, e.g. `jq -n '[limit(2; 1, 2, 3)]'` yields
-    `[1, 2]`, but when `n == 0`, `jq -n '[limit(0; 1, 2, 3)]'` yields `[1]` instead of `[]`.
-    And perhaps even worse, when `n < 0`, then `limit` yields *all* outputs from `exp`,
-    which is not documented.
 
   </details>
 * **Performance**: