Dominik Helm

> create a dedicated domain class only for computing stack frame tables Which is exactly what the TypeCheckingDomain is

Are those thrown exceptions necessary? Wouldn't it be sensible to just do nothing in that case, since the code must be dead?

Dear Rohit, checking reachability is fairly straightforward: after you computed the call graph, get the callers property for the method you are interested in, either from the `CallGraph`: `cg.callersPropertyOf(method)` or...

There are also new forms of invokedynamic in recent Scala versions that should be considered

> This PR will still fail unit (and probably integration) tests since some computation for StringConstancy is missing (often times in the call graph computations that depend on the ClassForName...

Well, the analyses use "ANY string" or "NO string" depending on the soundness mode now when they cannot determine a string's value, right? So that (maybe combined with a very,...

> would this be performed inline in the fallback function that is passed at PropertyKey creation? Yes, exactly. I think we should have a look whether we can implement a...

Well, it is not much more code than `field.constantFieldValue.isDefined` and `field.constantFieldValue.get`. It would be the (open) fallback computation of the property, which cannot be restricted. And the framework wouldn't push...

That's the general expectation in OPAL anyway that properties are queried from the property store.

@maximilianruesch Is a fallback computation something you would like to look into?