-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in alterationx10/opinionated-zio
match types
#20858
Labels
Comments
Related to #18261 |
Gedochao
added
itype:bug
area:typer
regression
This worked in a previous version but doesn't anymore
labels
Jul 3, 2024
Minimization: type M[F[_, _]] = Int match
case 0 => String & M[F]
type A = M[[x,y] =>> x & y]
def Test: Unit =
val x: A = ???
val _: M[[x,y] =>> x & y] = x // error |
WojciechMazur
pushed a commit
that referenced
this issue
Aug 28, 2024
…21017) Before the changes, when comparing two `HKTypeLambda` result types, the list of binding pairs was lost when entering comparison of `AndOrType`s, which caused the `equals` to fail, and hence prevented hash-consing. Even though `M1` and `M2` in pos/i20858-min should still conform to one-another, we entered a deep-subtype comparison because of the order in which the TypeComparer does dealiasing of AppliedTypes, and comparison of MatchCases and AndTypes. Fix #20858 [Cherry-picked f2829c3]
prolativ
pushed a commit
that referenced
this issue
Nov 20, 2024
…21017) Before the changes, when comparing two `HKTypeLambda` result types, the list of binding pairs was lost when entering comparison of `AndOrType`s, which caused the `equals` to fail, and hence prevented hash-consing. Even though `M1` and `M2` in pos/i20858-min should still conform to one-another, we entered a deep-subtype comparison because of the order in which the TypeComparer does dealiasing of AppliedTypes, and comparison of MatchCases and AndTypes. Fix #20858 [Cherry-picked f2829c3]
prolativ
pushed a commit
that referenced
this issue
Nov 21, 2024
…21017) Before the changes, when comparing two `HKTypeLambda` result types, the list of binding pairs was lost when entering comparison of `AndOrType`s, which caused the `equals` to fail, and hence prevented hash-consing. Even though `M1` and `M2` in pos/i20858-min should still conform to one-another, we entered a deep-subtype comparison because of the order in which the TypeComparer does dealiasing of AppliedTypes, and comparison of MatchCases and AndTypes. Fix #20858 [Cherry-picked f2829c3]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
One more affected project
alterationx10/opinionated-zio
it's bisect points to the same commits. This time we don't have ambigious extension methods, yet, still type reduction failsyields:
Originally posted by @WojciechMazur in #20288 (comment)
The text was updated successfully, but these errors were encountered: