Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to using Scalameta/Scalafix's API? #265

Closed
dwijnand opened this issue Nov 9, 2018 · 2 comments
Closed

Switch to using Scalameta/Scalafix's API? #265

dwijnand opened this issue Nov 9, 2018 · 2 comments

Comments

@dwijnand
Copy link
Collaborator

dwijnand commented Nov 9, 2018

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?

@dwijnand
Copy link
Collaborator Author

I started investigating if this is possible by asking in the scalameta/scalameta Gitter room: https://gitter.im/scalameta/scalameta?at=5bd347d5db022f757af4cbae

@olafurpg then also shared that https://github.com/olafurpg/symtab-explorer is an example repo with basic main function.

@dwijnand
Copy link
Collaborator Author

This is "wontfix". While an interesting idea, MiMa (at least for now) will continue to be based on nsc and the non-pickle info in the bytecode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant