You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, there is a subtlety here. In the case of transparent type aliases, maybe we don’t want the compilation process to be impacted by the dealiasing process. But I see at least two good valid situations where we want the annotation to be taken into account: for opaque type aliases, and for abstract type members.
The text was updated successfully, but these errors were encountered:
Compiler version
3.0.0-RC1
Minimized code
https://scastie.scala-lang.org/KpsRCJFXRNOrDzfael6tbw
Output
The compilation error is:
Expectation
The compilation error message should display the content of the
@implicitNotFound
annotation. This is the case in Scala 2, FYI: https://scastie.scala-lang.org/YULABebLTOa66sTci8OLqgHowever, there is a subtlety here. In the case of transparent type aliases, maybe we don’t want the compilation process to be impacted by the dealiasing process. But I see at least two good valid situations where we want the annotation to be taken into account: for
opaque
type aliases, and for abstract type members.The text was updated successfully, but these errors were encountered: