[
https://issues.apache.org/jira/browse/GROOVY-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King resolved GROOVY-9308.
-------------------------------
Fix Version/s: 6.0.0-alpha-1
Resolution: Fixed
> [Parrot] support let or val keyword, aka "final var"
> ----------------------------------------------------
>
> Key: GROOVY-9308
> URL: https://issues.apache.org/jira/browse/GROOVY-9308
> Project: Groovy
> Issue Type: Wish
> Reporter: Matthias Fuchs
> Assignee: Paul King
> Priority: Minor
> Fix For: 6.0.0-alpha-1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I'm a long time java developer and I'm used to add "final" to my variable
> definition: final var name = "a"
> I think the "var" keyword itself helps a lot, but seeing "var" and "final
> var" not being alligned properly in code makes me crazy ;)
> As we have *def* and *var* in groovy, wouldn't it be nice to have a *val* or
> *let* in groovy too, that is just a short form of "*final var*"?
> Although personally I would prefer "val" I do understand that some people
> might have problems differentiating "var" and "val", hence the "let".
> Imagine:
> {code:java}
> var destination = "Wien"
> val country = "AT"{code}
> instead of:
> {code:java}
> var destination = "Wien"
> final var country = "AT"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
