Johannes Düsing

/it:test *EDIT:* This comment was used to test whether the changes introduced in #155 actually work as intended - which they seem to do, the job status is set to...

Alright, i've your not completely against that i'll have a more detailled look into those occurrances and post a PR 👍

I'm currently looking into this issue. For RTA, it's actually an easy fix, as we thought we just need to add some types to the BR `references.conf` under the key...

I have to be honest, i don't know much about Android, but we could ofc just leat the current `reference.conf` be the one designated for Android and provide an updated...

Regarding the preconfiguration: I'll look into it, maybe find a suitable analysis to gather such types and post a PR! 🤓 Regarding the propagation-based analysis: I looked into this a...

Closed with #241

I think you make a good point. I restructured parts of this PR so that now: * There is an `InitialInstantiatedFieldsKey` and corresponding `InstantiatedFieldsFinder` to detect fields that shall always...

Oh i forgot to mention: The `rta.InstantiatedTypesAnalysis` and `xta.InstantiatedTypesAnalysis` now both use the `InitialInstantiatedFieldsKey` for their respective initialization, thus (hopefully) fixing the issue that RTA could sometimes be less sound...

My latest commit adds support for the initial intantiated fields to CFA-1-0 and CFA-1-1. For the latter i had to create dummy allocation sites as the fields are defined in...

There are two points why i think the first option may be the better one: * Like you said, it's more specific and should keep loss of precision to a...