Darren Duncan schreef:
TSa:
And I still think that it is a good idea
to name the set operations after their equivalent boolean
connectives:
(|) union
() intersection
(^) symmetric difference
Well, and to make them Bag operations to start with.
To start off with, I agree with
Ruud H.G. van Tol writes:
Darren Duncan schreef:
TSa:
set operations ... make them Bag operations to start with.
I agree with ... making Set the main type and making Bag an
extension built upon that, as complex is built upon num, etc.
I don't think that will work out.
Smylers schreef:
Ruud H.G. van Tol:
Darren Duncan:
TSa:
set operations ... make them Bag operations to start with.
I agree with ... making Set the main type and making Bag an
extension built upon that, as complex is built upon num, etc.
I don't think that will work out. Modification of a
At 10:54 AM +0100 11/28/06, Ruud H.G. van Tol wrote:
To start off with, I agree with your comment about making Set the
main type and making Bag an extension built upon that, as complex is
built upon num, etc.
I don't think that will work out. Modification of a Set is more complex
than
HaloO,
Darren Duncan wrote:
This may be a non-issue from a user's viewpoint, but as a user, I want
set operations that have sets as input to return sets as output by
default. Eg, unioning 2 Set that have common values should return a Set.
First of all the operations could be overloaded.
HaloO,
as a spin-off of the 'Set-returning .keys (was Re: Smart Matching
clarification)' thread I want to propose the addition of a Bag
type that completes the set of immutable types. It shall have the
following properties.
1) It is a multiset generalization of Set
2) It is a supertype of Set
TSa writes:
I want to propose the addition of a Bag type
Different from the CBag that's already mentioned in Synopsis 3?
Smylers
At 7:08 PM + 11/28/06, Smylers wrote:
TSa writes:
I want to propose the addition of a Bag type
Different from the CBag that's already mentioned in Synopsis 3?
Smylers
TSa wasn't the first person to ask for an explicit Bag type. I did
too, a few weeks ago. And one reason for that was
Author: larry
Date: Tue Nov 28 17:27:59 2006
New Revision: 13483
Modified:
doc/trunk/design/syn/S06.pod
Log:
Distinguished Set and Bag values from KeySet and KeyBag containers.
Modified: doc/trunk/design/syn/S06.pod
TSa wrote:
1) It is a multiset generalization of Set
2) It is a supertype of Set and Seq (a Set can of course be build
from a Seq). That is 'Set does Bag' and 'Seq does Bag'. Note
that a Seq is a ready-made Bag and if it happens to have no
duplicates it behaves like a Set.
3) It has
Author: larry
Date: Tue Nov 28 19:22:48 2006
New Revision: 13484
Modified:
doc/trunk/design/syn/S06.pod
Log:
typo
Modified: doc/trunk/design/syn/S06.pod
==
--- doc/trunk/design/syn/S06.pod(original)
+++
At 5:28 PM -0800 11/28/06, [EMAIL PROTECTED] wrote:
Author: larry
Date: Tue Nov 28 17:27:59 2006
New Revision: 13483
Modified:
doc/trunk/design/syn/S06.pod
Log:
Distinguished Set and Bag values from KeySet and KeyBag containers.
snip
Ah, thank you. A nice clean-looking solution which
12 matches
Mail list logo
