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
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!
The text was updated successfully, but these errors were encountered:
(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 whenkentuckymule
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 calledScalaLibHelper
).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!The text was updated successfully, but these errors were encountered: