No, we don't, and I don't really see how they're more useful than
java.lang.reflect.Proxy (which we probably should provide some kind of
native support for). I mean, I don't precisely know the semantics of
this feature in Kotlin or Go, but isn't it just the same thing?
A data point: in the 100s of thousands of lines of Java code I have
written over the past three years, I don't believe I've written a
single "delegate". And I've certainly never run into a problem where
java.lang.reflect.Proxy would have been helpful. And I don't even have
multiple inheritance in Java! With Ceylon's inheritance model, I would
have even less use for delegates!
I would *much* rather have interception/instrumentation built into the
language as a feature of the metamodel, than "delegates".
Instrumentation is much more widely useful, and a better solution to
the things I've seen people use proxies for in Java.
It almost makes me want to repudiate the cute "decorators"
functionality in CDI...
> --
> You received this message because you are subscribed to the Google Groups
> "ceylon-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
ceylon-users...@googlegroups.com.
> To post to this group, send email to
ceylon...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/ceylon-users.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/ceylon-users/4a7527e4-4be2-426b-b544-33ac7ed70ac4%40googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
--
Gavin King
ga...@ceylon-lang.org
http://profiles.google.com/gavin.king
http://ceylon-lang.org
http://hibernate.org
http://seamframework.org