No, generally method names are verbs and class names are nouns. There is no verb for "making a tuple" which is a bit of a deficiency in the English language if anything; But all those linguistic details pale in comparison to the glaring hole of caching mutable results.
On Thursday, June 2, 2016 at 7:10:58 AM UTC+2, Kiran Kedlaya wrote: > > Eh? Shouldn't foo.list() return the same as list(foo) (a list) and > foo.tuple() the same as tuple(foo) (a tuple)? > > On Tuesday, May 31, 2016 at 6:08:51 AM UTC-7, Volker Braun wrote: >> >> I've said it before: list() should always return a tuple. Yes I know its >> called list, but its just an English thing that verb and noun can't be >> distinguished. Certainly no excuse to cache mutable data structures. >> >> On Tuesday, May 31, 2016 at 2:35:46 PM UTC+2, Jeroen Demeyer wrote: >>> >>> On 2016-05-31 14:06, Johan S. R. Nielsen wrote: >>> > And that the small >>> > penalty in returning a *copy* of the list in each call to list() is a >>> > small price to pay for mitigating user errors? >>> No. Better use a immutable data structure instead of a list. >>> >>> -- 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.
