I think it is a great idea for these functions to return valid nix
expressions, and to be able to directly write them to a file. I also
really like the idea of creating a named subset only containing literal
values.
However... I disagree about calling it something special other than just
a plain nix expression until the parser actually limits on what can be
in the file. As it is now, it would be just yet another term to know about.
I worry that without restrictions it makes the distinction meaningless,
and worse, creates files which are so-called "nixon" but may not
actually be. This could make it much more difficult later on to add
restrictions.
Best,
Graham
On 02/28/2016 08:54 AM, deCube.net | Danny Wilson wrote:
How about NEON
Nix Expression Object Notation
On 28 feb. 2016, at 15:49, stewart mackenzie <[email protected]
<mailto:[email protected]>> wrote:
Excellent idea, this removes quite a lot of manual steps.
Recently wrote some dirty python scripts to automate the checking and
replacing of sha256s, this approach would make it trivial, reducing
check times from about an hour and growing to mere seconds.
Though, I do have a reservation about the name. An unbubbled search
for NixOS almost always returns a 'did you mean Nixon?' It's
infuriating. Clojure's equivalent is Edn.
Might I encourage a wilder more adventures ... unambiguous name?
/sjm
_______________________________________________
nix-dev mailing list
[email protected] <mailto:[email protected]>
http://lists.science.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
[email protected]
http://lists.science.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
[email protected]
http://lists.science.uu.nl/mailman/listinfo/nix-dev
