I believe that’s a Go limitation… If some function has nil as an argument, it goes crazy (I’m 100% sure that statement is technically incorrect :P). But I have seen this many times in different contexts, and the rule of the thumb is: Use with – Don’t assume your function arguments to be non-nil.
Already open issue to track stracktrace due to nil