Skip to content

fix(SharedMemory): correct behavior with spare capacity and copy-on-write semantics. - #463

Closed
u-veles-a wants to merge 3 commits into
ppfrom
fix_shared_memory
Closed

fix(SharedMemory): correct behavior with spare capacity and copy-on-write semantics.#463
u-veles-a wants to merge 3 commits into
ppfrom
fix_shared_memory

Conversation

@u-veles-a

Copy link
Copy Markdown
Collaborator

Description

  • Update set_items_count method to enforce unique ownership before modifying item count.
  • Implement additional tests for SharedMemory and SharedVector to ensure correct behavior with spare capacity and copy-on-write semantics.
  • Enhance index write context tests to verify snapshot integrity during destination growth.

…rite semantics

Signed-off-by: Alexandr Yudin <57181751+u-veles-a@users.noreply.github.com>
@u-veles-a u-veles-a added this to the v0.8.7 milestone Aug 4, 2026
@u-veles-a
u-veles-a requested a review from cherep58 August 4, 2026 08:56
@u-veles-a u-veles-a self-assigned this Aug 4, 2026
@u-veles-a
u-veles-a requested a review from vporoshok as a code owner August 4, 2026 08:56
@u-veles-a u-veles-a added the bug Something isn't working label Aug 4, 2026
@vporoshok
vporoshok marked this pull request as draft August 5, 2026 18:29
@vporoshok vporoshok closed this Aug 6, 2026
@vporoshok
vporoshok deleted the fix_shared_memory branch August 6, 2026 10:08
@vporoshok vporoshok removed this from the v0.8.7 milestone Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants