Feature: Better error messages #24
Description
When a cast function raises unexpectedly it can be tricky to see what field actually caused it. This can be helped by unit testing the cast fns (so you are sure they handle the cases you expect) and then possibly IO.inspecting the value as it comes in. But it would be nicer to be able to see which field caused the error just straight off the bat.
The obvious thing to do would be to wrap the cast__fns in a try catch but I don't like that at all...