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

Feature: Jar/classpath parsing #8

Open
aaronlevin opened this issue Apr 20, 2018 · 0 comments
Open

Feature: Jar/classpath parsing #8

aaronlevin opened this issue Apr 20, 2018 · 0 comments

Comments

@aaronlevin
Copy link

aaronlevin commented Apr 20, 2018

(paraphrasing from @gkossakowski)

Currently, kentuckymule does not parse jars or look at the classpath for the code it is type checking. The sample code it's being tested against is the scala standard library which has a minimal set of dependencies (mostly or all in the java standard library?) and so when kentuckymule needs to search for information on one of these symbols, it uses a shim to avoid having to do proper jar and classpath parsing (the shim is called ScalaLibHelper).

This ticket tracks implementation of a proper jar parser to avoid having to use the shim. This would also empower kentuckymule to be run over other codebases, specifically the scala community build, which would help develop benchmarks to support collaboration!

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

No branches or pull requests

1 participant