Skip to content

Conversation

@franzpoeschel
Copy link
Contributor

@franzpoeschel franzpoeschel commented Dec 16, 2025

There is no reason why we should not. unique_ptr is less resource heavy than std::shared_ptr, and especially the ADIOS2 backend uses some optimizations based specifically on unique_ptr.
Users may still provide shared_ptr-based fallbacks, examples/12_span_write.cpp tests this.

Note: We still have some scattered untested instances of std::string and bool overloads scattered here and there for dataset-related operations. With #1774, we are now more explicit about which overloads we instantiate. This led to having to remove some of these wrong instances now with this PR, especially from the Python API.

no reason why we shouldnt
@franzpoeschel franzpoeschel added this to the 0.17.0 milestone Dec 16, 2025
@ax3l ax3l self-requested a review December 17, 2025 12:22
@ax3l ax3l self-assigned this Dec 17, 2025
@ax3l ax3l merged commit 2b255f6 into openPMD:dev Dec 17, 2025
30 checks passed
franzpoeschel added a commit to franzpoeschel/openPMD-api that referenced this pull request Dec 17, 2025
* Use std::unique_ptr in Span API fallback

no reason why we shouldnt

* Remove unused string overloads

* Remove support for boolean types
franzpoeschel added a commit to franzpoeschel/openPMD-api that referenced this pull request Dec 17, 2025
* Use std::unique_ptr in Span API fallback

no reason why we shouldnt

* Remove unused string overloads

* Remove support for boolean types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants