There's something pretty weird in the behavior of ...
# reflect
s
There's something pretty weird in the behavior of reflect. I have a value class wrapping a UUID (which while investigating this, I've realized might be a bit pointless). I have a data class containing that value class, and upon reflection, it is not null, when in fact it is null. If the same class is a normal class instead, in reflection it's null as expected. Is this a bug in reflect or am I just crazy for using a value class in this way?