Yann Hamdaoui

## Preamble In the following, **PM** is used for **p**ackage **m**anager. We explored the following possibilities: 1. A lockfile based system, Nickel-specific, where a dedicated tool would do all the...

Thanks for the hindsight, @Gabriel439. It sounds like we underestimated the URL route :confused: > This makes me think that there is a solution that we haven't been considering yet...

Actually, adding an `hidden` meta annotation to show fields that are not to be serialized is something that I've been considering for a long time, and that feels natural. From...

>I think that if you have “first class metadata“, then they need to be strict (the spine needs to be strict, actual content of the field, hidden behind a |...

Most probably due to recursive records (which currently withhold all fields in the environment of each field, even when the fields are not recursive at all). The implementation of #330...

> But the problem is that we need to design fields for being overridden. By which I mean that any field which is not explicitly marked with `default` will consider...

I see. So maybe we should support both, such that standard usage can still use a simple overriding operator, without depriving other users from thix NixOS modules approach.

You're right, even if the semantics would be slightly different, because the `//` I propose would keep the priority unchanged when both sides have the same priority while your solution...

This wouldn't be hard to do I think, using metavalues to store this information, without much overhead. Then the `query` sub-command could show this information along the value. > `(import...

> My first idea would be to force casing of type identifier to start with uper case letter and variables with lower case. But I realy do not think of...