Summary: | [1.8][quick assist] Conversion between lambda expression and method reference not semantically equal on instance method | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Viliam Anirud <viliam> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, markus.kell.r, noopur_gupta, shorttail, stephan.herrmann, viliam |
Version: | 4.7 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Whiteboard: | stalebug | ||
Bug Depends on: | 353759 | ||
Bug Blocks: | 449106 |
Description
Viliam Anirud
2016-08-17 16:51:46 EDT
When the receiver is a local variable, the language rules already enforce that it be effectively final. Such a rule does not exist for fields, so, yes, in this case the point in time when the receiver value is captured is relevant, and the refactoring invisibly changes this. Although the Quick Assist is not completely semantically preserving, it may still be useful depending on the circumstances. I don't think we should disable the Quick Assist in this case, but we should mark it as potentially dangerous with the facility from bug 353759 (which is not implemented yet). *** Bug 520434 has been marked as a duplicate of this bug. *** This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |