Scala 3's -Yexplicit-nulls about sbt-tpolecat HOT 5 OPEN

Is it ready for use? e.g. @SethTisue on Discord a few months ago:

seconded that -Yexplicit-nulls isn't really that usable yet, but I just want to note that it's being worked on: scala/scala3#18112

https://discord.com/channels/632150470000902164/632150470000902166/1131611679566872698

from sbt-tpolecat.

Anyway, in general -Y flags should be considered guilty until proven innocent. -Y is a signal that something is internal and/or not-ready-for-prime-time

from sbt-tpolecat.

I'd enable it 🤷‍♂️

sbt-tpolecat is a plugin that enables errors in case of unused imports or unused variables, and there's nothing more annoying than that.

The “platform types” in Kotlin are well implemented, as the compiler is also looking at @NonNull and @Nullable annotations from Java's ecosystem. I hope that Scala implements that as well, but meanwhile, while we're waiting, I want explicit nulls for protection against Java APIs, and I don't mind using .nn all over the place.

from sbt-tpolecat.

IMHO this issue also seems like a major impediment to using explicit nulls.

• scala/scala3#15891

This use of Option is idiomatic for handling possibly-null values, so it seems ironic that it isn't available when using explicit nulls.

from sbt-tpolecat.

That untagged unions aren't used yet in the stdlib is such a pity, as it would improve type safety by a lot.

from sbt-tpolecat.