Reports common usage patterns of java.util.Map that could be replaced with Java 8 methods: getOrDefault(), computeIfAbsent(), putIfAbsent(), merge(), or replaceAll().
Signed-off-by: Lars Grefer <eclipse@larsgrefer.de>
Advice calling protected super method causing java.lang.VerifyError 'Bad access to protected data'
Also expanded test to cover protected field access as well as methods
Fix required getting the correct receiver type for both field access and method
calls to correspond to Java's complicated rules for accessing protected
members (JLSv2 6.6.2 and mentioned in passing in JVMv2 5.4.4)
expanded coverage and fix for bug involving around advice with either
assert or <name>.class in the body
the fix for now is just to not inline such advice, but in the future these
should be transformed to inlinable constructs
Half-way through refactoring of ResolvedTypeX's and Worlds. This
should make incremental compilation and using binary aspect libraries
work MUCH better.
The current state doesn't fix any of those issues, but it also does
continue to pass all of the existing tests.
redesign of making members used in around bodies accessible
this design is confiined to the aspect containing the around entirely which
makes for cleaner implementation issues and lets things like super calls
be implemented correctly.