Earlier quoted context omitted.
It does not. I think your parent must have been doing something strange; if you have a *const T, one that's null will still be a Some. It's &T, which cannot be null by definition, that uses the null value as None, since it cannot be null.
I was actually using mut/ const and got this bug, I don't think I used &T since I was handling raw memory addresses.
If you can reproduce you should file a bug.