`pass` instruction
supki opened this issue · comments
So, the reason we have pass in our fork of a popular library is that that library returns Either String TemplateRenderingResult. There, when we abort template rendering with something akin to die, we would have to parse the string (which is actually a pretty-printed error) and retrieve the reason for dying from it, which is cumbersome.
If we can avoid having String-like types in our API, pass is unnecessary, since we can pattern on Error instead.