Until you want to create a bunch of posets that may be the same, or worse, check if they are a lattice. However, unless you're storing a strong reference to the poset, you don't run into memory problems as the UniqueRepresentation is a weak cache. So if you are running out of memory, there is a leak somewhere. Plus it will cause problems for people who have defined coercion maps by removing UniqueRepresentation.
Best, Travis On Wednesday, September 30, 2015 at 10:42:05 AM UTC-5, Nathann Cohen wrote: > > > However, it is a drawback of posets being unique > > representations as we don't want to check for being a lattice when > passing > > data. > > > > We might also want to > > consider moving over to a UniqueFactory. > > We might also want to remove this dependency of posets on > UniqueRepresentation. Despite creating this equality problem, > UniqueRepresentation also causes a memory problem by caching *all* > created posets in memory (makes some computations impossible). > Similarly, it is also responsible for slowness upon creation of > Posets, as every new poset is compared with the others. > > Nathann > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
