Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:JDT Core/Plan/4.8/JEP286"
(Created page with "==Comments for page version of 2017-11-20== * '''Grammar''': yes, avoiding any grammar changes sounds great. * '''Errors''': ** "Cannot use 'val' ...", should read 'var', righ...") |
m (→Comments for page version of 2017-11-20) |
||
| Line 5: | Line 5: | ||
* '''DOM''': we need to define a strategy for getType() methods of VariableDeclarationExpression and VariableDeclarationStatement, where we don't have a type reference (AST) to answer, but answering null is probably not an option, either. | * '''DOM''': we need to define a strategy for getType() methods of VariableDeclarationExpression and VariableDeclarationStatement, where we don't have a type reference (AST) to answer, but answering null is probably not an option, either. | ||
* '''Quick fix''': is specifying the allocation type (implementation) better then declaring the variable type? I think the opposite is the case. Inversely, for documentation purposes, a quick fix to change 'var' to the inferred type could be useful, IMHO (support lazy typing, consolidate later). Of course all this is a matter of style. | * '''Quick fix''': is specifying the allocation type (implementation) better then declaring the variable type? I think the opposite is the case. Inversely, for documentation purposes, a quick fix to change 'var' to the inferred type could be useful, IMHO (support lazy typing, consolidate later). Of course all this is a matter of style. | ||
| + | [[User:Stephan.herrmann.berlin.de|Stephan.herrmann.berlin.de]] ([[User talk:Stephan.herrmann.berlin.de|talk]]) 08:33, 21 November 2017 (EST) | ||
Revision as of 09:33, 21 November 2017
Comments for page version of 2017-11-20
- Grammar: yes, avoiding any grammar changes sounds great.
- Errors:
- "Cannot use 'val' ...", should read 'var', right?
- DOM: we need to define a strategy for getType() methods of VariableDeclarationExpression and VariableDeclarationStatement, where we don't have a type reference (AST) to answer, but answering null is probably not an option, either.
- Quick fix: is specifying the allocation type (implementation) better then declaring the variable type? I think the opposite is the case. Inversely, for documentation purposes, a quick fix to change 'var' to the inferred type could be useful, IMHO (support lazy typing, consolidate later). Of course all this is a matter of style.
Stephan.herrmann.berlin.de (talk) 08:33, 21 November 2017 (EST)