Skip to content
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 durban/choam - type argument does not conform to upper bound #22596

Open
jchyb opened this issue Feb 13, 2025 · 3 comments
Open
Assignees
Labels
area:typer itype:bug regression This worked in a previous version but doesn't anymore

Comments

@jchyb
Copy link
Contributor

jchyb commented Feb 13, 2025

https://github.com/VirtusLab/community-build3/actions/runs/13209505213/job/36881113788

Compiler version

Works: 3.6.3
Broken: 3.6.4-RC1

Minimized code

abstract class MutHamt[K <: Hamt.HasHash, V <: Hamt.HasKey[K], I <: Hamt[_, _, I]]

abstract class Hamt[K <: Hamt.HasHash, V <: Hamt.HasKey[K], H <: Hamt[K, V, H]]

object Hamt {
  trait HasKey[K <: HasHash]
  trait HasHash
}

Output

[error] ./main.scala:1:80
[error] Type argument I does not conform to upper bound Hamt[? <: Hamt.HasHash, ? <: Hamt.HasKey[Hamt[?, ?, I]#K], I]
[error] abstract class MutHamt[K <: Hamt.HasHash, V <: Hamt.HasKey[K], I <: Hamt[_, _, I]]
[error]                                                                                ^

Expectation

No error.
Already submitted once here, but didn't get fixed with the closing PR, so perhaps it was unrelated to that regression after all.

@jchyb jchyb added itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label labels Feb 13, 2025
@jchyb jchyb changed the title Regression in durban/choam - type argument does not conform to upper bound Regression in durban/choam - type argument does not conform to upper bound Feb 13, 2025
@jchyb
Copy link
Contributor Author

jchyb commented Feb 13, 2025

Bisect points to 26ecda5

@jchyb jchyb added area:typer regression This worked in a previous version but doesn't anymore and removed stat:needs triage Every issue needs to have an "area" and "itype" label labels Feb 13, 2025
@Gedochao
Copy link
Contributor

This means the bisect points to the same commit as #22585.
Possibly a common root cause.
cc @dwijnand

@mbovel
Copy link
Member

mbovel commented Feb 23, 2025

This issue was picked for the Scala Issue Spree of tomorrow, Monday, February 24th. @dwijnand and @nmcb will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:typer itype:bug regression This worked in a previous version but doesn't anymore
Projects
None yet
Development

No branches or pull requests

4 participants