Should null-safe operators always return null or return primitives when requested?

[nicholashagen]

Currently, primitive properties on the right side of a lookup will return a default primitive value for a null-safe operation.

user = null as User;
user?.age // returns 0 if age is defined as int getAge()

This may be better off returning null and always an Object wrapper so that you can differentiate between invalid (null) and valid (potentially 0).

[jaxzin]

+1 for returning null and hiding the Java concept of primitives from Tea

On Sep 28, 2012, at 10:57 PM, Nicholas Hagen notifications@github.com
wrote:

Currently, primitive properties on the right side of a lookup will return a
default primitive value for a null-safe operation.

user = null as User;
user?.age // returns 0 if age is defined as int getAge()

This may be better off returning null and always an Object wrapper so that
you can differentiate between invalid (null) and valid (potentially 0).

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/198.