Michael Färber

Thanks for the bug report, @pkoppstein, and thanks for the detailed analysis, @kklingenberg! I believe that the problem is not that the file lives long enough; it is because the...

Thank you for your solution, it worked for me as well: $ ocaml -I `camlp5 -where` camlp5o.cma

@oguz-ismail, I'm sorry to hear that you feel like your time has been wasted. However, jaq implement a sufficiently large set of jq features that I think that it warrants...

Thanks a lot for reporting this, @pkoppstein! I was not aware that definitions were allowed at such positions. Supporting this will require a breaking change to the syntax, so my...

Hi @tusharmath! I have already thought about making the jaq value type more flexible, in order to support use cases like yours. I suppose that an approach like @wader's could...

(Thanks, @wader, by the way for explaining how you do it in `fq`.)

@tusharmath, I created a trait in jaq called [`ValT`](https://github.com/01mf02/jaq/blob/1699a7d1fc7ede6f728fcaa243f011137fcc220a/jaq-interpret/src/val.rs#L62) that will eventually allow you to use jaq with any kind of data type that implements this trait. However, so far...

@tusharmath, I'm happy to hear that you can implement `ValT`. I plan to release a new stable jaq version this week, and I plan to make the `ValT` trait public....

@wader, the "survival" of jq values is preserved by the introduction of the `ValT` trait, as it happens independently from `ValT`. For example, see the [implementation of `.` (identity filter)...

This would probably make a nice first issue if someone wants to work on this. :)