You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From our discussion on Tuesday: in general, we should not add a catch mechanism to the language, but having a specific mechanism such as assertThrows or assertError would be useful for testing.
The text was updated successfully, but these errors were encountered:
This would be great. There's a parallel discussion going on in Nix right now about whether their equivalent to this (called tryEval) should return details about the error. The argument against providing details is that they can reveal evaluation order, which is pretty icky in a pure language like this.
I also need something like this for NixOS/nixos-homepage#78 where I need to be able to catch all errors so that evaluation of one package can't break evaluation of an other one. (see here: fkz/nix@61dc5a7)
From our discussion on Tuesday: in general, we should not add a catch mechanism to the language, but having a specific mechanism such as
assertThrows
orassertError
would be useful for testing.The text was updated successfully, but these errors were encountered: