Skip to content

Dependent type information lost to compiler through 2nd dependent type #8730

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

Closed
scabug opened this issue Jul 16, 2014 · 1 comment
Closed

Comments

@scabug
Copy link

scabug commented Jul 16, 2014

I put together a gist which demonstrates the issue: https://gist.github.com/wheaties/7192b40b76cb99e79127

The same issue exists both in SBT and at compile time. Essentially by instantiating a class containing a dependent type through the use of dependent types, that type is lost. If, instead the same object is created directly, the type information is preserved.

It is similar to #5700 with one exception, an explicit type is given always.

@scabug
Copy link
Author

scabug commented Jul 16, 2014

Imported From: https://issues.scala-lang.org/browse/SI-8730?orig=1
Reporter: Owein Reese (wheaties)
See #5700

@scabug scabug closed this as completed Nov 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant