On Tue, Dec 12, 2017 at 8:06 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-12-11 18:35, Simon King wrote: >> >> Well, we want to mix in P.category().element_class (an abstract class) >> into whatever P prescribes for its elements. So, P.element_class >> should be a class whose mro also contains abstract element classes >> defined in the category. >> >> What I did not say is that the mechanism to construct the element class >> of P should be coded in the category framework. > > > Maybe you are misunderstanding me. I am *not* talking about determining the > element class. I talking about the mechanism, *given* the element class, to > *construct* instances of that class.
I agree that an abstraction of the general mechanism could be implemented in one place. For example there's no reason I can see that Category._make_named_class needs to be in Category. It's already written in a pretty abstract manner. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
