Issues

yq: a literal or constructor after a stage that matched nothing is one node in yq (`.a[] | 1` over `a: []` is `1`), nothing here

rust-works/succinctly#6943 · opened

on Nov 11, 2026

yq: a lone `!` on an empty node is the empty string, where yq reads null (`a: !`)

rust-works/succinctly#6942 · opened

on Nov 11, 2026

yq: a flow mapping's key with no value keeps the line break before a blank line and the closer (`{k⏎⏎}`), and a comment after it is a parse error

rust-works/succinctly#6941 · opened

on Nov 11, 2026

yq: tag of a zero-padded 08 after a write is !!int, and !!int 0_8 reads as a string (#6927 follow-up)

rust-works/succinctly#6938 · opened

on Nov 11, 2026

yq: a tab right after a quoted scalar or an alias in block context is a parse error (`a: "b"\t`)

rust-works/succinctly#6937 · opened

on Nov 11, 2026

1

yq: to_yaml, @yaml and tostring of a value the filter copies, reorders or writes print block where yq keeps the node's style (#6901 follow-up)

rust-works/succinctly#6933 · opened

on Nov 11, 2026

yq: an arithmetic error writes `()` where yq writes each keyed operand's key (#6904 follow-up)

rust-works/succinctly#6930 · opened

on Nov 11, 2026

yq: an explicit `!!int 08` becomes the float 8.0 in JSON across the reindex bridge (#6899 follow-up)

rust-works/succinctly#6927 · opened

on Nov 11, 2026

1

yq: -p props|csv|tsv|base64|uri|kyaml|xml|toml|hcl|lua|ini input formats and -o/-p auto by extension (#6850 slice 3)

rust-works/succinctly#6925 · opened

on Nov 11, 2026

yq: -o kyaml|xml|toml|hcl|lua|ini output formats (#6850 slice 2)

rust-works/succinctly#6924 · opened

on Nov 11, 2026

yq: an -o encoder error prints earlier results, and -e reads the value, not the encoded text (#6850 follow-up)

rust-works/succinctly#6923 · opened

on Nov 11, 2026

yq: -o=props lacks comments and the --properties-separator / --properties-array-brackets / --csv-separator flags (#6850 follow-up)

rust-works/succinctly#6922 · opened

on Nov 11, 2026

1

jq: read a lone regular-file stream in windows so peak memory does not grow with the input (#6913 follow-up)

rust-works/succinctly#6920 · opened

on Nov 11, 2026

docs: user-facing guide to choosing between jq and succinctly jq, backed by the compare results (#5409 follow-up)

rust-works/succinctly#6916 · opened

on Nov 11, 2026

compare(jq): add a >=1 GB tier for streaming and early-exit rows (#5409 follow-up)

rust-works/succinctly#6915 · opened

on Nov 11, 2026

compare(jq): time and measure piped stdin input, not only file arguments (#5409 follow-up)

rust-works/succinctly#6914 · opened

on Nov 11, 2026

1

perf(yq): a write over a document with no presentation still builds two full comment trees, 169 MiB of the 436 MiB peak at 20 MiB (#6815 follow-up)

rust-works/succinctly#6880 · opened

on Nov 10, 2026

1

perf(yq): a YAML write materializes the document as an OwnedValue twice, 62 MiB of the 436 MiB peak at 20 MiB (#6815 follow-up)

rust-works/succinctly#6879 · opened

on Nov 10, 2026

2

compare(jq): add a Neoverse (and M1 Max) run to the generated comparison (#5409 follow-up)

rust-works/succinctly#6873 · opened

on Nov 10, 2026

yq: -p/-o accept only yaml, json and auto; yq's kyaml, props, csv, tsv, xml, base64, uri, toml, hcl, lua, ini and shell formats are not tracked anywhere

rust-works/succinctly#6850 · opened

on Nov 10, 2026

3

yq: an update body that reads the member it writes, deletes then writes, or is not a chain of writes still changes only a merging mapping's copy; a source replaced with new keys and a chained merge differ (#6827 follow-up)

rust-works/succinctly#6838 · opened

on Nov 10, 2026

1

yq: a plain scalar or key, a comment line and a root block scalar's first blank line still read U+0085, U+2028 and U+2029 as content (#6369 residuals)

rust-works/succinctly#6820 · opened

on Nov 10, 2026

4

perf(yq): every result is held in memory before the first prints; jq mode answers the same query in a sixth of the memory (#5865 M1)

rust-works/succinctly#6813 · opened

on Nov 10, 2026

2

yq: an empty `{}` is one mapping whatever the fan-out before it, where succinctly yq builds one per node (#2427 follow-up)

rust-works/succinctly#6801 · opened

on Nov 10, 2026

5

yq: an `ireduce` body keeps an accumulator list (multi-output UPDATE) and reads an absent key as nothing, where succinctly yq folds like jq (#2427 follow-up)

rust-works/succinctly#6802 · opened

on Nov 10, 2026

4

Navigation Menu

Repository navigation

Issues

yq: a literal or constructor after a stage that matched nothing is one node in yq (`.a[] | 1` over `a: []` is `1`), nothing here

yq: a lone `!` on an empty node is the empty string, where yq reads null (`a: !`)

yq: a flow mapping's key with no value keeps the line break before a blank line and the closer (`{k⏎⏎}`), and a comment after it is a parse error

yq: tag of a zero-padded 08 after a write is !!int, and !!int 0_8 reads as a string (#6927 follow-up)

yq: a tab right after a quoted scalar or an alias in block context is a parse error (`a: "b"\t`)

yq: to_yaml, @yaml and tostring of a value the filter copies, reorders or writes print block where yq keeps the node's style (#6901 follow-up)

yq: an arithmetic error writes `()` where yq writes each keyed operand's key (#6904 follow-up)

yq: an explicit `!!int 08` becomes the float 8.0 in JSON across the reindex bridge (#6899 follow-up)

yq: -p props|csv|tsv|base64|uri|kyaml|xml|toml|hcl|lua|ini input formats and -o/-p auto by extension (#6850 slice 3)

yq: -o kyaml|xml|toml|hcl|lua|ini output formats (#6850 slice 2)

yq: an -o encoder error prints earlier results, and -e reads the value, not the encoded text (#6850 follow-up)

yq: -o=props lacks comments and the --properties-separator / --properties-array-brackets / --csv-separator flags (#6850 follow-up)

jq: read a lone regular-file stream in windows so peak memory does not grow with the input (#6913 follow-up)

docs: user-facing guide to choosing between jq and succinctly jq, backed by the compare results (#5409 follow-up)

compare(jq): add a >=1 GB tier for streaming and early-exit rows (#5409 follow-up)

compare(jq): time and measure piped stdin input, not only file arguments (#5409 follow-up)

perf(yq): a write over a document with no presentation still builds two full comment trees, 169 MiB of the 436 MiB peak at 20 MiB (#6815 follow-up)

perf(yq): a YAML write materializes the document as an OwnedValue twice, 62 MiB of the 436 MiB peak at 20 MiB (#6815 follow-up)

compare(jq): add a Neoverse (and M1 Max) run to the generated comparison (#5409 follow-up)

yq: -p/-o accept only yaml, json and auto; yq's kyaml, props, csv, tsv, xml, base64, uri, toml, hcl, lua, ini and shell formats are not tracked anywhere

yq: an update body that reads the member it writes, deletes then writes, or is not a chain of writes still changes only a merging mapping's copy; a source replaced with new keys and a chained merge differ (#6827 follow-up)

yq: a plain scalar or key, a comment line and a root block scalar's first blank line still read U+0085, U+2028 and U+2029 as content (#6369 residuals)

perf(yq): every result is held in memory before the first prints; jq mode answers the same query in a sixth of the memory (#5865 M1)

yq: an empty `{}` is one mapping whatever the fan-out before it, where succinctly yq builds one per node (#2427 follow-up)

yq: an `ireduce` body keeps an accumulator list (multi-output UPDATE) and reads an absent key as nothing, where succinctly yq folds like jq (#2427 follow-up)