-
Notifications
You must be signed in to change notification settings - Fork 21
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
Typer hangs with implicits that return TypeTags (regression from 2.10) #8992
Comments
Imported From: https://issues.scala-lang.org/browse/SI-8992?orig=1 |
@xeno-by said: |
@TiarkRompf said: |
@TiarkRompf said: |
@xeno-by said (edited on Dec 6, 2014 10:40:20 PM UTC): When trying to resolve the overload for What happens then is caused by the aforementioned bugfix. In 2.10.x, tupleToDense2 implicit candidate is triaged without resolving implicit arguments (the A: Arith context bound), whereas in 2.11.x typedImplicit1 is changed to resolve implicit arguments during triaging. Therefore in 2.11.x, the mere fact of considering tupleToDense2 as an implicit conversion, will launch an implicit search for Arith[A]. Now, a bunch of implicit methods provide Arith[Something], and, what's worse, triaging those implicit methods will cause other Do you think it would be possible for you to restructure the code so that this avalanche of implicit lookups doesn't get spawned? |
@TiarkRompf said: This particular case with |
Scala 2.11 can't type this over night, but 2.10 runs quickly.
The text was updated successfully, but these errors were encountered: