Optional<Float32> weird behavior

Clearly the type inference is not the smartest there. Upcoming preview should handle this case better.

Regarding the coloring: indeed, issue was that two styles got combined (error and unused) which in turn led to that very dark red. In upcoming the system will no longer apply the unused style (transparent) if error style is already in place. Thanks for pointing it out.

2 Likes