Nullable class operator Implicit(Value: Nullable<T>): T

BIZ TMS Aurelius
1

We got an issue several times, because of Implicit class operator:

class operator Implicit(Value: Nullable<T>): T

In several cases, we changed Fields to Nullable.
So there are possible a lot locations, where this Field is used directly.

Because of this class operator, compiler doesn't give a hint or error, that types does not fit.
This will also raise an error in runtime, because of possible Null-Values.

Is it possible to change this Implicit to GetValueOrDefault?
I know, that this is a big impact / change in this behaviour, but I think it would make things a lot easier.

2

Unfortunately, no.

I know, that this is a big impact / change in this behaviour

Exactly.
And to add to that, that's not the behavior we want. The current behavior is the desired one, anyway.

3

Maybe you could add some global config, so that we could configure this behaviour?

4

It's really not the correct behavior for nullable. And nullables are used everywhere, a test for a global config in the getter of each and every nullable read will have a performance penalty.