Profpatsch
Profpatsch
> * _Interactive_: provide Nix with the Nickel interpreter as an artifact, and enable him to execute Nickel code. However this looks complex, as it requires the modification of the...
> Nickel would rather be a superset of Nix. > a full fledged program may contain constructions which are not straightforward to compile to Nix, at least at first sight:...
Maybe I’m understanding this wrong and you *need* a wrapping `[|` and `|]` for it to be unambiguous. But then why not something like `
What I want to say is that a two-character separator is harder to type unless it uses the same symbol multiple times. `[|` means I have to type two different...
Personally I’m not a big fan of list comprehensions, as they can be expressed fully with simple higher-order functions. They complicate the language, and thus the work of implementors. If...
I would also add an exhaustiveness check if `..` is not used (see https://discourse.dhall-lang.org/t/exhaustive-record-field-matching/75/1 for motivation). e.g. * `let { foo } = { foo = "abc", bar = "cde"...
We can put the output of the docs generator that @german1608 is working on.
Chiming in to give some cheers :1st_place_medal:
@SupraSummus Code generation has the disadvantage that you can’t directly influence how fast your implementation is going to be (especially when mapping from a functional paradigm to an imperative/interpreted paradigm)....