Robert Hensing

In 2.18, it really is a keyword and not a variable reference that adheres to scope rules etc. In the repl, it evaluates to `null` now, which I'd consider to...

I quite like the syntax @mkenigs used in #4004 to talk about overrides ``` A (override B.C.D.E) -> B (override C.D)-> C -> D -> E ``` It is also...

> Note that the above replaces the graph structure of the current lock file format with a simple tree. - current graph: everything, ready to for a `mapAttrs` and `fix`...

> would be represented on the lockfile side in much the same way as the `follows` approach. Yes, except `follows` doesn't have to be in the lockfile at all. We...

> (it's a bit more like an implicit follows). An implicit follows is an override just as well. ----- Also responding to your previous comment: > Implementing `useLock` would require...

@szlend Thank you for looking into this. I think the solution in #10218 and in this proposal are somewhat incompatible, because #10218 would require fetching all lock files all the...

The point of this issue is to add native literals to the language. I'm sure Nixpkgs can implement `lib.fromHex` quite well, but that'd be a function from string to integer....

Oh no! I forgot about the list item separator... This proposal _does_ steal usable syntax: ``` nix-repl> let x10 = "x number ten"; in [ 0x10 ] [ 0 "x...

This seems over-engineered, and the base 32 wouldn't match Nix's own base32 encoding; lack of base 64 would be surprising. I'd like to reserve `_` as an ignored digit group...

We might also want to steal syntax such as `64Ki == 65536` to represent the base 2 unit prefixes (`Ki`, `Mi`, `Gi`, etc), although that opens up more questions about...