On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > My vote: > >> [X] Phase out properties which perform any non-trivial computation > > > In certain cases, properties might be useful (but it could very well be that > there are 0 such cases in Sage).
I generally feel that properties *should* be used in general for invariants of some object, regardless of how it's computed in the first place. I see the point about not using them for "non-trivial" computations but I also find the lack of a clear definition of "non-trivial" troubling. I agree with Jeroen that there may be exceptions. I think a strict rule against "properties in public APIs" is asking for trouble, and that this should still be considered on a case-by-case basis. Perhaps more controversially, I'm fond of creating proxy objects that can become callable if need be For example an int that usually has an invariant value, but in might rare cases can be modified by some additional context that would be provided by "calling" it, in which case I make a proxy-int that's callable. I think in these cases Sage's policy has been to make them methods with zero required positional arguments, which is fine too. It's my preference, but it also has downfalls, so it's not a sword I care to die on :) Erik -- 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.
