Travis

I agree. That second change is almost exactly what I used in my code right now as a work around. I also think the second way matches semantically with what...

That looks good to me. If I'm reading it right, a non-nil error always has a non-nil cause, which was my original issue. The only thing I might suggest is...