Yup, we've had this issue for a while https://issues.apache.org/jira/browse/GROOVY-4757 Would be great to fix it with the Parrot parser.
On Thu, Jan 19, 2017 at 9:59 AM, Marcin Erdmann <[email protected]> wrote: > Sorry for stealing the thread, but there is one annoying thing that > relates to parsing modifiers in Groovy. Is there any chance to fix modifier > being mandatory for methods with generic signatures in Parrot? I.e. this is > now invalid: > > <T> T foo(T bar) > > and has to be written like this to be parsed: > > public <T> T foo(T bar) > > Is there a reason for the modifier to be required in that case other than > problems with parsing? > > I'm happy to file an issue for this if that is indeed considered to be an > issue. Please let me know which issue tracker I should use if that's the > case. > > Marcin > > On Thu, Jan 19, 2017 at 8:22 AM, Daniel Sun <[email protected]> > wrote: > >> > def is by now to be thought of as an alias for Object >> OK. I see. Thanks :) >> >> >> Cheers, >> Daniel.Sun >> >> >> >> -- >> View this message in context: http://groovy.329449.n5.nabble >> .com/The-order-of-modifiers-and-annotations-tp5737808p5737813.html >> Sent from the Groovy Dev mailing list archive at Nabble.com. >> > >
