Currently, providing the CollectionConverters object manually in the scala.jdk package as a part of Rho causes assembly issues, as projects with dependencies on Rho and the Scala Collection Compat will require conflicts to be resolved.
From what I understand, this was originally done to avoid bincompat issues during updates, as the collection compat library broke some rules early on. This has gotten a lot more stable and is pretty widely used now in the Scala ecosystem, so it seems much safer to include this library.
Another option could be to repackage the collection converters under a new namespace. I could work on that if that is preferred.
Currently, providing the CollectionConverters object manually in the scala.jdk package as a part of Rho causes assembly issues, as projects with dependencies on Rho and the Scala Collection Compat will require conflicts to be resolved.
From what I understand, this was originally done to avoid bincompat issues during updates, as the collection compat library broke some rules early on. This has gotten a lot more stable and is pretty widely used now in the Scala ecosystem, so it seems much safer to include this library.
Another option could be to repackage the collection converters under a new namespace. I could work on that if that is preferred.