Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we allow empty collections? #498

Closed
uscholdm opened this issue Jun 25, 2021 · 2 comments
Closed

Should we allow empty collections? #498

uscholdm opened this issue Jun 25, 2021 · 2 comments
Labels
closed: duplicate Duplicate issue or subsumed by another issue topic: collections Issues related to collections, membership, and ordering

Comments

@uscholdm
Copy link
Contributor

If members are added or removed from a collection and there are no members at a given time but some will be added, you have an empty collection. We don't want to have it cease to be a collection.

@rjyounes
Copy link
Collaborator

Is this a case we are likely to encounter in our modeling domains, or is it strictly theoretical?

If we allow empty collections, then the restriction on Collection has to be removed. In that case the class has no formal semantics.

@rjyounes rjyounes added the topic: collections Issues related to collections, membership, and ordering label Jul 23, 2021
@rjyounes rjyounes changed the title Should we allow empty collections Should we allow empty collections? Aug 9, 2021
@rjyounes rjyounes added the closed: duplicate Duplicate issue or subsumed by another issue label Sep 16, 2021
@rjyounes
Copy link
Collaborator

Duplicates #570.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate Duplicate issue or subsumed by another issue topic: collections Issues related to collections, membership, and ordering
Projects
None yet
Development

No branches or pull requests

2 participants