infinisil changed the topic of #nix-lang to: Channel for discussing Nix as a language - https://nixos.org/nix/manual/#chap-writing-nix-expressions - Logs: https://logs.nix.samueldr.com/nix-lang/
Dotz0cat has joined #nix-lang
Dotz0cat_ has quit [Ping timeout: 272 seconds]
rajivr has joined #nix-lang
ris has quit [Ping timeout: 246 seconds]
__monty__ has joined #nix-lang
manveru has joined #nix-lang
srhb has joined #nix-lang
Graypup_ has quit [Quit: ZNC 1.6.1 - http://znc.in]
Graypup_ has joined #nix-lang
ddellacosta has joined #nix-lang
Dotz0cat_ has joined #nix-lang
Dotz0cat has quit [Ping timeout: 240 seconds]
ris has joined #nix-lang
evanjs has quit [Ping timeout: 272 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
<infinisil> Hm, what if Nix was able to continue evaluation after evaluation errors
<infinisil> As in, it would just continue to the next "element" which would've been evaluated after the failing one
<infinisil> Evaluation then only errors once it can't find any more elements to evaluate
<infinisil> Then it would throw all evaluation errors at once
<__monty__> As someone who makes a lot of errors, the compiler/runtime telling me about more of them sooner sounds like a good thing : )
<infinisil> I guess it could also throw them right away, but still continue evaluation
<infinisil> Should probably be opt-in too
evanjs has joined #nix-lang
evanjs has quit [Ping timeout: 240 seconds]
evanjs- has joined #nix-lang
__monty__ has quit [Quit: leaving]