Closed tanishiking closed 1 year ago
So, isn't going back to li-haoyi/fastparse 3.0.1 (that depends on geny 1.0.0) and bump scalameta/scalameta as 5.0.0 (because it's not binary compatible by geny) an option?
We actually spend a considerable amount of effort to keep the binary compatibility, so I would say that currently it's not an option.
How much effort would it be to shade geny
, then?
How much effort would it be to shade
geny
, then?
Should be doable in a day I think when anyone has the time
Related issues
Current scalameta parser depends on forked version of fastparse, which depends on geny 0.6.5. Since, geny < 1.0.0, and geny 1.0.0 are binary incompatible, apps that depends on
scalameta
cannot update havegeny >= 1.0.0
.So, isn't going back to li-haoyi/fastparse 3.0.1 (that depends on geny 1.0.0) and bump scalameta/scalameta as 5.0.0 (because it's not binary compatible by geny) an option?