Cédric Chantepie
Cédric Chantepie
> It's also our responsibility as maintainers to incentivize others to move on. No it's not. Anorm is a standalone library. Not a framework. It should be as less intrusive...
Would be nice
I don't think it would make sense. Macro are compile time. That's clearly started in the Scala 3 migration guide that when using the compatibility mode, the macro won't be...
Having migrated "some" projects with macros, I doubt that really possible, if it is, it will increase drastically the complexity for play-json, but also for the project. Moreover, I don't...
Transitive dependency is a runtime point, not a compile time one. Even in a multi-module project, as play-json is available for both version, I don't see the point. A sub-module...
Rather than a PR, a show case of why it would be useful. For now, I don't see any legit case. > It can be used to create a new...
There is no "leave everything on scala 2.13". Latest Play-JSON version is avoid with same compile and run time feature for 2.13 and 3. For me, the link to the...
I would say that issue is related to the way it tried to mix submodules while migrating some of them. Even not considering macro that raise library management issue such...
I don't know what could be considered as official, but as a maintainer of macros on PlayJSON and other libraries, I won't go for it. For me mixing in library...
Hi, Scala 3 re-introduce exhaustivity in pattern matching check, so that's out of scope of the library.