Conversation
helly25
force-pushed
the
implement/hamt-key-extractors
branch
from
September 16, 2026 11:05
9053e20 to
4683af1
Compare
helly25
force-pushed
the
implement/hamt-key-extractors
branch
from
September 16, 2026 11:42
4683af1 to
70ba8a8
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flat HAMT maps and sets now expose explicit cross-source cloning, letting callers move a complete persistent value into the allocation domain whose guarantees they need. Ordinary copies remain cheap shared snapshots; changing domains is visible, fallible, and deep.
AG;DR
try_clone_to<OtherSource>(...)on persistent flat maps and sets;This is a draft stacked on the owned-domain clone layer in #479. It must remain unmerged until the implementation stack is reviewed and merge-ready as a whole.