Šimon Mandlík
Šimon Mandlík
**Is your feature request related to a problem? Please describe.** Currently, python queries cover only standard assignments like `x = 1`. Augmented assignments like `x += 1` could be supported...
This is my best attempt to further improve julia queries: * works for empty structures * works for `;` argument separation * adds `@assignment.*` queries Queries are not perfect, there...
### Did you check existing issues? - [X] I have read all the [tree-sitter docs](https://tree-sitter.github.io/tree-sitter/using-parsers) if it relates to using the parser - [X] I have searched the existing issues...
Reduce the TTXF (time to first execute) using [`PrecompileTools.jl`](https://github.com/JuliaLang/PrecompileTools.jl). [This](https://julialang.org/blog/2023/04/julia-1.9-highlights/#caching_of_native_code) is also a good resource and also [this](https://julialang.org/blog/2021/01/precompile_tutorial/) `Base.show` is a very good candidate.
Speed up load time of the package by using [package extensions](https://pkgdocs.julialang.org/v1/creating-packages/#Conditional-loading-of-code-in-packages-(Extensions)). Candidates: `SparseArrays`, `FillArrays`, `PooledArrays`, `Accessors` Bonus: do the same in [`JsonGrinder.jl`](https://github.com/CTUAvastLab/JsonGrinder.jl).
Currently, we do not optimize model in docs too much, which leads to borderline poor performance. Spend some time optimizing e.g. Recipes and Mutagenesis examples and add an "`Optimized`" section...
Implement similar tests for displaying the structures as in [`Mill.jl`](https://github.com/CTUAvastLab/Mill.jl/blob/master/test/io.jl), so that if something silently breaks, we know about it.
Implement structure `VectorizedScalarExtractor`, with which we could group the following extractor into a single node: ```julia julia> schema(JSON.parse.([ """ { "a": 1, "b": 2, "c": 3 } """, """ {...
Currently, the following fails: ```julia julia schema(["1", 1]) ERROR: InconsistentSchema at root: Can't store `Int64` into `LeafEntry{String}`! ``` which is ok as long as we want to process the data...
Study [`Mill.model_lens`](https://github.com/CTUAvastLab/Mill.jl/blob/a038f287fd1f2190666284d423a4ef17bec540db/src/util.jl#L185-L219) and [`Mill.data_lens`](https://github.com/CTUAvastLab/Mill.jl/blob/a038f287fd1f2190666284d423a4ef17bec540db/src/util.jl#L221-L254) and implement the same functionality for schemas / extractors in this package. Bonus: make it work with the `Mill.jl` versions as well. That is, make it...