>> Isn't it a bug that we don't see a ValueTypeNode at the call? > > No, because the value type is nullable. It's only known to be non-null after the receiver null check > and that's when we can/should create the ValueTypeNode. That makes sense and the change looks to me. Roland.