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/
sphalerite has quit [Ping timeout: 258 seconds]
rajivr has joined #nix-lang
ddellacosta has quit [Ping timeout: 256 seconds]
__monty__ has joined #nix-lang
sphalerite has joined #nix-lang
pingiun has joined #nix-lang
ddellacosta has joined #nix-lang
kalbasit_ has joined #nix-lang
kalbasit has quit [Ping timeout: 256 seconds]
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nix-lang
kalbasit_ has quit [Ping timeout: 240 seconds]
kalbasit has joined #nix-lang
kalbasit has quit [Ping timeout: 240 seconds]
kalbasit has joined #nix-lang
kalbasit_ has joined #nix-lang
kalbasit has quit [Ping timeout: 240 seconds]
davidtwco has quit [Read error: Connection reset by peer]
davidtwco_ has joined #nix-lang
<puck> > -9223372036854775808
<{^_^}> error: invalid integer '9223372036854775808'
<puck> > (-9223372036854775807 - 1)
<{^_^}> -9223372036854775808
<puck> :)
<lukegb> oh no
<puck> >:)
<lukegb> >:D
<__monty__> That's fairly standard no? Two's complement is asymmetrical and unary minus is probably parsed as "invert the parsed positive number."
<puck> > let or = 5; foo.bar = 6; quux = 7; in [ foo.bar or quux or ]
<{^_^}> [ <CODE> ]
<puck> > :p let or = 5; foo.bar = 6; quux = 7; in [ foo.bar or quux or ]
<{^_^}> [ 6 ]
<puck> __monty__: well, it's an edge case that isn't being handled
<__monty__> Now that's a weird parse.
<__monty__> Why isn't the final or causing a parse error because there's no second argument?
<__monty__> Is it parsed as (quux or)?
<__monty__> > :p let or = 5; foo.bar = 6; quux = 7; in [ foo.bar or quux or ]
<{^_^}> [ 6 ]
<__monty__> > :p let or = 5; foo.bar = 6; quux = 7; in [ foo.baz or quux or ]
<{^_^}> error: attempt to call something which is not a function but an integer, at (string):460:52
<__monty__> Guess os.
<__monty__> *so
__monty__ has quit [Quit: leaving]