Issue: Version 0.4.1 creates Type Exception on getOrElse

[zellidev0]

I noticed when using 0.4.1 in contrast to 0.4.0 a type exception is thrown when using getOrElse on Option.

type '() => String' is not a subtype of type '() => Never' of 'orElse'

The code responsible for the error is:

model.activeProfile
           .map((final Profile profile) => profile.isActive)
           .getOrElse(() => false)

Is this a known issue? Downgrading to Version 0.4.0 from 0.4.1 works.

[zellidev0]

@SandroMaglione Can you elaborate what the issue exactly was? I tried to understand the PR but it just seems to change dependency versions.

[SandroMaglione]

@ju851zel you can read details in #92

The issue was with introducing a const factory constructor for None. When calling map, it caused the type to be wrong at runtime.

[qwertylolman]

well, it's not fixed. i got
type '() => TaskEither<L, R>' is not a subtype of type '() => TaskEither<L, Never>' of 'orElse'<…>

My issue was next:
Option.none().toEither(() => Exception('some message')).toTaskEither();
after toTaskEither I got an TaskEither<Exception, Never> instead of TaskEither<Exception, T>

workaround is Option extension:
option.match(
() => TaskEither<L, T>.leftTask(Task(onNone)),
(s) => TaskEither<L, T>.right(s),
)

similar problem with Option.toIOOption
workarounds
IOOption toIOOption1() => //
IOOption(() => this);