Best [ractice to describe complex type value that can be null

[Алексей Винокуров]

I wonder what's "officially" recommended for something like this

function getComplexType():ComplexType

in case that sometimes returned value can be null. Is Null<ComplexType> returned type preferable to describe that value can be null or it leads to some runtime issues and type inference drawbacks. For example static extension doesn't recognize such nullable type as "clean" first argument.

[Gama11]

The standard library sometimes uses Null<T> as self-documentation in that way, that's probably as "official" as it gets. There are several instances of this in haxe.macro.Expr for example: https://github.com/HaxeFoundation/haxe/blob/3.2.1/std/haxe/macro/Expr.hx#L182

[Stephane Le Dorze]

If you do not want to miss some 'null' values, then wrap that with an Option, it's safer at the cost of some (small?) overhead.

function getComplexType():Option<ComplexType>

[Laurence Taylor]

You can also try stx_maybe, which is an abstract type over Null<T>

https://github.com/0b1kn00b/stx_maybe

haxelib install stx_maybe

using hx.Maybe;

regards,
Loz

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.