Why is a keyword better than an annotation from an IDE developer's
perspective (considering Groovy already has tons of annotations which
more complex semantics than @PackageScope) ?
On 13.12.2017 23:14, Daniil Ovchinnikov wrote:
This is the best way from IDE perspective.
—
Daniil Ovchinnikov
JetBrains
jetbrains.com <http://jetbrains.com>
“Drive to develop"
On 14 Dec 2017, at 01:03, Nathan Harvey <nathanwhar...@gmail.com
<mailto:nathanwhar...@gmail.com>> wrote:
In Java, methods and fields use package scope by default. In Groovy,
they
use public. In order to make something package scope, you have to use the
@PackageScope annotation. This makes code look a bit messy but also
doesn't
seem very intuitive. What if the "package" keyword was able to be
applied,
in exactly the same way as "public" and "private" are?
Example:
package void foo() {}
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
