Re: [golo-dev] Augmentation scope

[Julien Ponge <julien.ponge@xxxxxxxxxxxx>]

Perhaps in these kinds of cases dynamic objects are a better fit, since the newly attached methods need to be instance-scoped.

Or we’d need something like “persistent” augmentations, which are more or less what prototype-based languages do.

- Julien

> On 11 Aug 2015, at 13:28, Yannick Loiseau <me@xxxxxxxxxxxx> wrote:
> 
> While this could be an interesting improvement, I'm not sure it would solve the given issue, since it's actually a reverse importation problem. Maybe I misunderstand what you mean.
> 
> 
> Le 10 août 2015 17:31:04 CEST, Julien Ponge <julien.ponge@xxxxxxxxxxxx> a écrit :
> Hi,
> 
> This is a very interesting topic.
> 
> How about something like transitive imports, i.e., something like:
> 
>   module Plop
> 
>   import transitive foo.Bar
> 
> in which case importing Plop also makes foo.Bar available at the consumer tail of imports.
> 
> The idea is to keep a middle-ground between what we have now (which is restrictive), and meta-classes / global augmentations.
> 
> Thoughts?
> 
> - Julien
> 
> 
> 
> golo-dev mailing list
> golo-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/golo-dev
> 
> 
> -- 
> Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
> _______________________________________________
> golo-dev mailing list
> golo-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/golo-dev