Github user srowen commented on the issue:
    Yes that's better IMHO. It makes this more consistent. Word2Vec was the 
only case that looked for an exact match on nullability when it was expecting 
nullable input (i.e. pointlessly disallowed non-null input)

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to