[sage-devel] Re: `ModuleElement` is forced though `Element` should be enough by the category framework

2019-02-27 Thread Kwankyu Lee
> > > In particular, Jeroen, concerning the strange rule that _lmul_ not being > implemented means that it returns None: I seem to recall (but I am not > 100% sure) that P._get_action_(Q) (or some other method name, I don't > recall) could test what happens if P.zero()._lmul_(Q.zero()) or

[sage-devel] Re: `ModuleElement` is forced though `Element` should be enough by the category framework

2019-02-26 Thread Simon King
Hi Jeroen, On 2019-02-27, Jeroen Demeyer wrote: > By the way, why is it an issue in the first place? Is there any reason > why you don't want to inherit from ModuleElement? I don't know what Kwankyu has in mind, but conceivably it is possible to have a parent that, depending on input

[sage-devel] Re: `ModuleElement` is forced though `Element` should be enough by the category framework

2019-02-26 Thread Simon King
Hi Kwankyu, On 2019-02-26, Kwankyu Lee wrote: > Since my parent is in the category of modules over QQ, then I think > elements of the parent should be automatically treated as module elements, > and using `Element` should just be ok. > > What do you think? I think that speed matters. I see