You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MiMa doesn't currently use many Scala-specific aspects from the bytecode. There's a few little bits and pieces, but it mostly doesn't parse the pickled Scala signatures.
This is the major blocker to #34 and the tickets associated with it.
I started to unblock that in #257, but didn't complete the effort.
(As a side note, depending on nsc is problematic for API stability/release reasons too: #193)
So my idea was: why not switch to more modern tooling, with fresh and documented APIs, like Scalameta? In researching this idea I'm told that Scalafix might have some APIs over Scalameta that might be appealing.
But before that: thoughts on the idea?
The text was updated successfully, but these errors were encountered:
MiMa doesn't currently use many Scala-specific aspects from the bytecode. There's a few little bits and pieces, but it mostly doesn't parse the pickled Scala signatures.
This is the major blocker to #34 and the tickets associated with it.
I started to unblock that in #257, but didn't complete the effort.
(As a side note, depending on nsc is problematic for API stability/release reasons too: #193)
So my idea was: why not switch to more modern tooling, with fresh and documented APIs, like Scalameta? In researching this idea I'm told that Scalafix might have some APIs over Scalameta that might be appealing.
But before that: thoughts on the idea?
The text was updated successfully, but these errors were encountered: