Qhesz

A `json.Decoder` opt-in would be better than nothing. I'll have a look at making a pull request.

Edit: the code already lets custom `UnmarshalJSON` handle nulls, I was wrong. ~A note about implementation: when I define my own type, I should be able to define whether it...

Just thinking out loud, you could wrap the `foo.Value` in your own type like: ``` type FooValue foo.Value //or type FooValue struct { foo.Value } ``` And override `UnmarshalJSON` to...

It doesn't seem that creative - but I appreciate the compliment nonetheless! This is the exact same thing you do if you want to add json serialisation to an existing...

Whoops, my point 5 is wrong - I misread the source code. It is possible to write your own `UnmarshalJSON` that is strict about nulls. The existing code will call...

Being wrong about 5 also means that if I wanted to use strictNulls, include 3rd party types like `time.Time`, and have them also be strict about nulls, I would have...

I can't see 3rd party types ever being fixed to be strict. They can't change the current `UnmarshalJSON` behaviour, because that's a breaking change. And there is no context provided...