The same scenario works for native-syntax aspects, but not for @<!---->AspectJ-style ones. See the currently deactivated test Bugs199Tests.testAsyncProceedNestedAroundAdviceThreadPool_gh128, which simply needs to be un-ignored in order to have a ready-to-use test case for a future implementation.
kriegaex
commented
8 months ago
This is work related to, but out of scope of bug #128 and PR #132. See https://github.com/eclipse/org.aspectj/pull/132#issuecomment-1054114608 and subsequent comments for details.
The same scenario works for native-syntax aspects, but not for @<!---->AspectJ-style ones. See the currently deactivated test
Bugs199Tests.testAsyncProceedNestedAroundAdviceThreadPool_gh128, which simply needs to be un-ignored in order to have a ready-to-use test case for a future implementation.