Viktor Kleen
Viktor Kleen
Update the revision of `tree-sitter-nickel` and copy over the highlighting queries. Also, adjust the `auto-pairs` configuration, since `'` isn't a paired delimiter in Nickel.
Implement a prototype solution for lazy imports. This feature can, for now, be accessed via the intentionally annoying syntax `import %lazy% "..."`. Semantically, the intention is to delay any filesystem...
Currently, for a Nickel program like `{ field | { foo } }`, the JSON documentation generated by `nickel doc` contains a pretty printed `{ foo, }` as a string...
Consider the following Nickel record: ```nickel { foo.bar.baz = 1, bar.baz.foo = foo.bar.baz + 1 } ``` This evaluates to the same term as `{ foo.bar.baz = 1, bar.baz.foo =...
As noted by @yannham in #1361, it would be useful to support `_` delimiters in numbers, e.g. `1_000_000`. In CUE for example, numbers are allowed to carry SI and IEC...
Inspired by this discussion question: https://github.com/tweag/nickel/discussions/1458. We should have error messages point at a particular field definition in a record, when that makes sense. For example, the code ```nickel let...
**Is your feature request related to a problem? Please describe.** When trying to use the partial configurations approach in Nickel, it is common to write a top-level record like ```nickel...
The following program rigthfully produces a contract blame error: ```nickel let foo | String -> Dyn = fun x => x in let bar = fun x => foo x...
The program ```nickel { foo : [| Dyn |] -> { bar : Dyn, baz : Dyn } = null } ``` produces the error ``` error: statically typed field...