On 2021-08-05 14:39, Paul King wrote:
> Marcin, I know we didn't progress, but do you recall whether we created an
> issue last time?
Good point Paul :-/. I should created a ticket to be able to track and
and be visible in grooming.
I've just created one for further consideration:
https://issues.
Thanks!
On Sat, Aug 7, 2021 at 2:36 AM Marcin Zajączkowski wrote:
> On 2021-08-05 14:39, Paul King wrote:
> > Marcin, I know we didn't progress, but do you recall whether we created
> an
> > issue last time?
>
> Good point Paul :-/. I should created a ticket to be able to track and
> and be visi
Marcin, I know we didn't progress, but do you recall whether we created an
issue last time?
On Thu, Aug 5, 2021 at 10:08 PM Marcin Zajączkowski wrote:
> I've been asking about the same thing back in 2020 with some proposals,
> but unfortunately without any reply:
>
> https://mail-archives.apache
I've been asking about the same thing back in 2020 with some proposals,
but unfortunately without any reply:
https://mail-archives.apache.org/mod_mbox/groovy-users/202001.mbox/%3cb62eefce-5d71-f394-8024-f2dd93c12...@wp.pl%3e
Nevertheless, maybe this time something constructive will be determined.
Since the delegation is effectively a part of a closure type, I’d expect
@DelegatesTo to have TYPE_USE target.
Of course, it’s now tailored for parameters, so it probably should be a
different annotation.
`genericTypeIndex` and `target` doesn’t make sense in TYPE_USE, so we are left
with `value
It is possible to define Closures for annotations, e.g., Spock's
`@Requires({ os.windows })`.
However, it is currently impossible to tell the IDE what this annotation
will delegate to, as @DelegatesTo is only applicable for parameters.
Could we either allow @DelegatesTo for TYPE_USE or mabe add a
