-
Bug
-
Resolution: Won't Fix
-
Medium
-
3.2.0
-
None
-
Severity 2 - Major
In CLOV-1596 we've prepared a solution for JDK8 streams based on rewriting expression-like lambda functions into lambda code blocks. However, this technique cannot be applied to method references (as we don't know number of arguments to be passed).
Figure out how to fix this.
Ideas:
- type casts -> not promising
- chaning signature to "<T> T lambdaInc(int, T, int)" -> not promising
- dedicated lambdaInc wrappers -> promising but very complex
- ...
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Instrumentation of method references with no compilation errors
-
-
Resolution: Won't Fix
-
Medium
-
3.2.0
-
None
-
Severity 2 - Major
In CLOV-1596 we've prepared a solution for JDK8 streams based on rewriting expression-like lambda functions into lambda code blocks. However, this technique cannot be applied to method references (as we don't know number of arguments to be passed).
Figure out how to fix this.
Ideas:
- type casts -> not promising
- chaning signature to "<T> T lambdaInc(int, T, int)" -> not promising
- dedicated lambdaInc wrappers -> promising but very complex
- ...
-
Unassigned
-
Marek Parfianowicz
- Affected customers:
-
1 This affects my team
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: