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

basyx.provider: Add SetObjectStore to provider #340

Merged
merged 3 commits into from
Jan 20, 2025

Conversation

zrgt
Copy link
Contributor

@zrgt zrgt commented Nov 21, 2024

SetObjectStore is backed by a set.
It does not have a problem with not updated ids as DictObjectStore (See #216).

I suppose the DictObjectStore or SetObjectStore normally do not contain so many Identifiables,
that iteration becomes a perfomance issue.

SetObjectStore is backed by a set.
It does not have a problem with
not updated ids as DictObjectStore (See eclipse-basyx#216).
@Frosty2500
Copy link
Contributor

LGTM 👍

@s-heppner
Copy link
Contributor

The code LGTM, but what's the use case for a SetObjectStore?

@s-heppner
Copy link
Contributor

As discussed in our meeting, both DictObjectStore and SetObjectStore have their advantages and disadvantages.
We document these in the docstrings of the classes and provide both in the future.

@s-heppner s-heppner changed the base branch from main to develop January 14, 2025 13:21
@zrgt
Copy link
Contributor Author

zrgt commented Jan 20, 2025

@s-heppner notes with explanations of dis-/advantages were added

@s-heppner s-heppner merged commit b178a8c into eclipse-basyx:develop Jan 20, 2025
14 checks passed
@s-heppner s-heppner deleted the add/set_object_store branch January 20, 2025 15:30
@s-heppner s-heppner added this to the Release v1.1.1 milestone Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants