<sterni>
catch is not pure for a definition of independent of eval order
<sterni>
unsure if eelco's comment is from a perspective of eval order is indeterministic or eval order may change in the future
<Profpatsch>
exceptions in a lazy language are a garbage fest
<Profpatsch>
better not depend on anything, especially not eval order
<Profpatsch>
like, tryEval itself is already highly dubious and should be banned really
<Profpatsch>
this is a slippery slope if I’ve seen one
<ekleog>
exception monad or gtfo
V has joined #nix-lang
<sterni>
I guess tryEval is somewhat fine as it only catches user generated errors anyways and doesn't tell you anything about it
<sterni>
but honestly that is something you can also emulate in pure nix without tryEval if you need to
<sterni>
but then you have yants probably :p
mpickering has quit [Read error: Connection reset by peer]
mpickering has joined #nix-lang
<infinisil>
sterni: You can't practically, because then every code path along the way needs to be made to work that way
<sterni>
infinisil: yeah it's definitely not viable for real world usage (nixpkgs)
<Profpatsch>
Unless languages like rust just make it viable
<Profpatsch>
And everybody in the nooooo you can’t just return errors like a normal person crying nerd camp is taken aback by haha, Result<a, err> go brrrrrrr
<Profpatsch>
“but it’s so inefficient”
<infinisil>
Profpatsch: Meanwhile we have a clustefuck of error handling in Haskell hah