Developers of Sympa

[Soji Ikeda <address@concealed>]

I think wrapper module Sympatic is not required (I don’t know why this option 
is ignored).

If Moo is required, use Moo in the source. If it is not, don’t use it.
What we need is to decide whether we use it or not.
We need not tasking our brain to decide whether  we prepare cryptic import 
option for it or not.
For example, if I propose to include MooX::Singleton, what will we do?

Instead of thinking about what is to be included in Sympatic, let’s think 
about how we will use.

Regards,
— Soji


2018/03/16 0:24、David Verdin <address@concealed>のメール:

> I would agree with that. If Moo is indeed used in the majority of modules, 
> it makes sense to use it as default and explicitly say when it is not 
> needed.
> 
> After all, it's only the reverse of previous behaviour.
> 
> Regards,
> 
> David
> 
> 
>> On 27/02/2018 13:38, Marc Chantreux wrote:
>> hello,
>> 
>> somewhere in the autodie thread, racke told us that Moo should be
>> included by default. this idea made its path in my mind as i was
>> defending autodie: the whole thing is to try to have the good defaults.
>> So i come back on it and try to defend the idea of racke (racke please
>> complete if i miss something important).
>> 
>> * most of the sympa files are objects so we should at least have Moo as
>>  default as racke suggest.
>> * even if you don't need Moo in your script, Moo will be loaded anyway
>>  by a dependency so there is no reduction of startup time or memory
>>  consumption.
>> * Moo comes with few keywords we probably should avoid in other contexts
>>  (has, extends, ...)
>> 
>> so i finally join the racke proposition
>> 
>>    use Sympatic;
>> 
>> should use Moo and MooX::*
>> 
>>    use Sympatic -noo; # no oo
>> 
>> can become the current behaviour in the very rare cases you want to
>> avoid Moo.
>> 
>> regards
>> marc
> 
> -- 
> "Mieux vaut viser la perfection et la rater que viser la médiocrité et 
> l'atteindre."
> - Francis Blanche
> 
>