Ólafur Páll Geirsson
Ólafur Páll Geirsson
@MasseGuillaume I estimate that would at least take several days to implement
How about adding them as properties to the spec? We already have scala-specific modifiers like `implicit` so it makes sense IMO to do the same for `native` or `synchronized`.
Thank you for reporting! Can we work around this by changing the exported name?
The most robust solution is to remove the custom coursier resolution and let build.sbt generate a resource file with the resolved classpaths. My concern with that approach is that it...
Thanks for reporting! I think we can fix this problem by adding `metacp.Settings.displayOut: nio.file.Path` (name up for debate) next to `Settings.out` https://github.com/scalameta/scalameta/blob/0745d22c31f12b789193450ff5eafe851d75e363/semanticdb/metacp/src/main/scala/scala/meta/metacp/Settings.scala#L9 Then we can - add `Settings.withOut(out: nio.file.Path)` method...
I think we should add occurrences to `classOf`
This looks like a great plan! Thank you for initiating this discussion. What 2.13 dependencies cause most problems for downstream users? I’m curious if we can replace them somehow so...
Is it possible to use the 2.13 tasty reader to upgrade those dependencies to Scala 3?
You are right, that will cause problems for 2.13 artifacts. Can we inline those dependencies instead (excluding protobuf) to make them disappear? Both geny and sourcecode are tiny, and I...
It would of course be ideal if we can build Scalameta against Scala 3, but the checklist above shows that it will require a lot of effort. There shouldn't be...