Repository navigation
Conversation
|
would be good to rebase this one. Might be something for early NB 29? (freeze for NB28 is about a week away) |
|
|
|
test sees to have found something. moving to NB32 |
| <apidef name="javasource_base">Java Source API</apidef> | ||
| </apidefs> | ||
| <changes> | ||
| <change id="parseTypeScope"> |
There was a problem hiding this comment.
Is it intentional to replace an old API change record with the new one?
| for (TreePath tp : selectionExits) { | ||
| if (tp.getLeaf().getKind() == Tree.Kind.RETURN) { | ||
| if (!exitsFromAllBranches) { | ||
| //TODO: the same for yield |
|
apichange in the PR that need discussion as per review, moving to next milestone |
395986f to
e8bb91e
Compare
|
Consider the following code snippet: Select these lines: Introduce Method leads to uncompilable source code, where |
…ble declared in the selection, we cannot introduce method unless the new method will exit from all branches (i.e. won't need to return boolean).
Thanks. I've tried to fix: we unfortunately cannot do the introduce method in this case, as we would need to different exit types. |
Consider code like:
Select these lines:
In the Alt-Enter popup, choose
Introduce Method.... This leads to:which is obviously wrong - it should be something like:
This patch attempts to change the introduce hint to do the correct transformation.
closes #8278
PR approval and merge checklist: