> We definitely should allow to specify any constructor for list-like
> objects (list, tuple, vector). Depending on the context, you may want
> the result to be hashable, to have further properties (like being a
> vector and doing linear algebra), that is mutable, ...
>
> Now what should be the def
On Thu, Nov 19, 2009 at 01:00:11PM +0100, Florent hivert wrote:
> > Is there any particular reason why when one tries to iterate over
> > IntegerVectors(k,n) one gets the vectors represented as lists and not
> > tuples?
Nothing really but a historical choice to port things from
MuPAD-Combinat as
Dear Tzango,
> Is there any particular reason why when one tries to iterate over
> IntegerVectors(k,n) one gets the vectors represented as lists and not
> tuples? The only difference between the two that I can think of is
> that lists are mutable and tuples aren't. I cannot see why being
> m
Hi,
Is there any particular reason why when one tries to iterate over
IntegerVectors(k,n) one gets the vectors represented as lists and not
tuples? The only difference between the two that I can think of is
that lists are mutable and tuples aren't. I cannot see why being
mutable is an advantage. On
