Dominik Helm
Dominik Helm
Please have a look at https://github.com/opalj/opal/blob/develop/DEVELOPING_OPAL/tools/src/main/scala/org/opalj/support/info/CallGraph.scala This might already be able to do what you want or at least show you how call graphs are generated with OPAL now. You're...
If you want to exclude libraries, just don't include them when instantiating your `Project`. You can also supply them as the second parameter to `Project` to have OPAL load the...
Which call graphs did you try? I think the first problem should not exist for the `AllocationSiteBasedPointsToCallGraphKey` (i.e., 0-1-CFA). This is by design, though, at least in theory, we could...
The example for the change necessary in Project was class `scala.collection.mutable.IndexedSeqView$AbstractTransformed`, method `public scala.collection.IterableFactory iterableFactory()` (the class is found in `OPAL/bi/src/test/resources/classfiles/scala-2.12.4/scala-library-2.12.4.jar`. This is defined in two interfaces: `scala.collection.mutable.Iterable` (implemented via...
True, the `scala.collection.View` and `scala.collection.mutable.Iterable` in this case came from Scala 3.5.0
/it:test
Thank you. If you find the time, any help in locating the new error would be helpful.
Had a glance at your changes and they seem fine, even if quite complex. I don't have an answer for the other one. Not computing this for dead code seems...
The tests failing don't seem related to the l0.TypeCheckingDomain, which worries me. They might come from the TypeLevelReferenceValues, which is a whole different beast.