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
In the application of the method foo, when determining the expected type of the third argument (which, according to the method signature, refers to the second argument), the typechecher wrongly uses the first argument, of type Int.
The text was updated successfully, but these errors were encountered:
@adriaanm said:
(In r23010) closes #1569, #3731: refactored dependent method types to get rid of debruijn indices and use singleton types instead.
this is the core of the dependent types refactoring, no implicit or inference changes
(one baffling discovery: resultType should drop annotations that don't subclass TypeConstraint, even in the trivial case... wow -- thanks to Tiark for helping me figure it out on a terrace in Barcelona
TODO: probably need a more principled approach to the propagation of plugin type-annotations)
The following code includes a method with a dependent type. It should normally typecheck (when using the option -Xexperimental of the Scala compiler).
However the compiler (version 2.7.2.final) signals the following
error.
In the application of the method foo, when determining the expected type of the third argument (which, according to the method signature, refers to the second argument), the typechecher wrongly uses the first argument, of type Int.
The text was updated successfully, but these errors were encountered: