-
Notifications
You must be signed in to change notification settings - Fork 1.1k
byname implicit depending on recursive given crash #8182
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
Comments
This would be fixed if we could do extension methods without resorting to ExtMethodApply |
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jan 8, 2021
Move some code out of `adapt` and `assignType`, to be re-used later in `typedSelect`. The aim of the refactoring is to move all select-dependent adaptations and re-tries into typedSelect. Right now some are in `adapt` and some are in `assignType`. This is awkward since it means that - we do too much in `TypeAssigner`. Sine it aims to be minimal `TypeAssigner` should have no business doing adaptations and retries. - wo do some adaptations too early in `adpt`. This means we need the cludge of wrapping trees in `ExtMethodApply` which causes scala#8182, among others.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jan 8, 2021
Move some code out of `adapt` and `assignType`, to be re-used later in `typedSelect`. The aim of the refactoring is to move all select-dependent adaptations and re-tries into typedSelect. Right now some are in `adapt` and some are in `assignType`. This is awkward since it means that - we do too much in `TypeAssigner`. Sine it aims to be minimal `TypeAssigner` should have no business doing adaptations and retries. - wo do some adaptations too early in `adpt`. This means we need the cludge of wrapping trees in `ExtMethodApply` which causes scala#8182, among others.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jan 11, 2021
The aim of the refactoring is to be clearer and to be able to drop ExtMethodApply. Two main strategies: 1. Move some code out of adapt and assignType into typedSelect. 2. Concentrate extension method expansion and conversions for selections in a method `tryExtensionOrConversion. The method is called from `typedSelect` and `tryInsertImplicitOnQualifier`. The aim of the refactoring is to move all select-dependent adaptations and re-tries into typedSelect. Right now some are in adapt and some are in assignType. This is awkward since it means that - we do too much in TypeAssigner. Sine it aims to be minimal TypeAssigner should have no business doing adaptations and retries. - we do some adaptations too early in adpt. This means we need the kludge of wrapping trees in ExtMethodApply which causes scala#8182, among others. Fixes scala#8182
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jan 15, 2021
The aim of the refactoring is to be clearer and to be able to drop ExtMethodApply. Two main strategies: 1. Move some code out of adapt and assignType into typedSelect. 2. Concentrate extension method expansion and conversions for selections in a method `tryExtensionOrConversion. The method is called from `typedSelect` and `tryInsertImplicitOnQualifier`. The aim of the refactoring is to move all select-dependent adaptations and re-tries into typedSelect. Right now some are in adapt and some are in assignType. This is awkward since it means that - we do too much in TypeAssigner. Sine it aims to be minimal TypeAssigner should have no business doing adaptations and retries. - we do some adaptations too early in adpt. This means we need the kludge of wrapping trees in ExtMethodApply which causes scala#8182, among others. Fixes scala#8182
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
minimized code
Crash output (click arrow to expand)
The text was updated successfully, but these errors were encountered: