For 'construct', the documentation doesn't say much about memory
usage:
construct : List S -> %
++ \spad{construct(x, y, ..., z)} returns the collection of
elements \spad{x, y, ..., z}
++ ordered as given. Equivalently written as \spad{[x, y, ..., z]$D}, where
++ D is the domain. D may be omitted for those of type List.
Although the convention is that in 'x:=construct(y)', x and y doesn't
share structure,
but there is serious violation, in IndexedList:
construct l == l pretend %
I wonder whether we should allow shared structure in 'construct',
after all we allow
shared structure in 'concat'.
> Again, I think deepcopy is not needed. As the semantics for deepcopy I
> would like to have: "no part of the original shares memory with any part
> of the copy".
Yes, deepcopy is not necessarily needed. And it might be very difficult
to implement.
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
