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
[scala/bug#11010] Put back Coll for compatibility reasons #7380
Conversation
The collection API was refactored. The internal type `Coll` was removed in new factories. To avoid breaking compatibility, we put it back in new factories for sub-types. See scala/bug#11010
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Small nit: I think it would be grammatically better to say "Use X directly" than "Use directly X"
Co-Authored-By: grizio <gaetan@rizio.fr>
Co-Authored-By: grizio <gaetan@rizio.fr>
Co-Authored-By: grizio <gaetan@rizio.fr>
Co-Authored-By: grizio <gaetan@rizio.fr>
I just passed some hours but I did not find how to suppress the error:
My knowledge on the matter is very limited. Except by impacting the rest of the collection, I do not see how to remove this error. |
I tried again, but I do not find how to correct the compilation issue without impacting the design. |
@NthPortal I haven't followed this... should this be revived in some form, or should we let it lie? |
actually let's discuss at scala/bug#11010 instead |
The collection API was refactored.
The internal type
Coll
was removed in new factories.To avoid breaking compatibility, we put it back in new factories for sub-types.
See scala/bug#11010