Here is the problem I see with this approach (which I have seen multiple
times now since I joined the ML):
1. The (oftentimes imho plausible) argument for introducing something
new in Groovy is, that current support is too cumbersome (as with
Daniel's proposal).
2. The suggestion then is, to stick with the current variety, and see
how much uptake it gets in the community.
3. But evidently there is a contradictio in se here: If one agrees that
current support in Groovy is too cumbersome, uptake will naturally
not be high, which is then taken to imply that Groovy users don't
want that feature at all (hence there is no need to make its use
less cumbersome). Case closed.
So I feel one should either state that one does not agree with the
assumption of usability of a feature being bad, or bring another
argument. Otherwise over time it feels just like a polemic trick to "let
people down easy"...
I understand that introducing new syntax or features to a language has
to be carefully considered, as to not back oneself into a corner etc.
But this proposal looks quite harmless to me, as well as being
syntactically sound. Which I might be mistaken about, of course - but
then one sentence should suffice to point out problematic areas :-)
Cheers,
mg
On 21.10.2018 00:42, Paul King wrote:
I am not against a shortened form but I'd wait and see how usage
of @Groovydoc goes first.
If it's use is extremely popular it would make sense to consider
shortcuts.
On Sun, Oct 21, 2018 at 4:22 AM Guillaume Laforge <glafo...@gmail.com
<mailto:glafo...@gmail.com>> wrote:
I find that a bit too cryptic.
I prefer it to be more explicit, even if a bit more verbose.
On Sat, Oct 20, 2018 at 3:28 PM Daniel.Sun <sun...@apache.org
<mailto:sun...@apache.org>> wrote:
Hi all,
Current switch for runtime groovydoc is a bit verbose,
i.e.
`@Groovydoc` is a bit long. For example,
```
/**
* @Groovydoc
* some groovydoc here
*
*
```
I propose a new switch as follows(a `@` appended to
`/**`):
/**@
*
* some groovydoc here
*
*
```
Any thoughts?
Cheers,
Daniel.Sun
-----
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from:
http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
--
Guillaume Laforge
Apache Groovy committer & PMC Vice-President
Developer Advocate @ Google Cloud Platform
Blog: http://glaforge.appspot.com/
Twitter: @glaforge <http://twitter.com/glaforge>
