Repository navigation
refactor(moonbit): use ordered maps for async handle registries - #1756
Draft
peter-jerry-ye wants to merge 1 commit into
Draft
peter-jerry-ye wants to merge 1 commit into
peter-jerry-ye wants to merge 1 commit into
Conversation
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.
Component Model handles are supplied by the host and may be sparse. Replace the generated MoonBit runtime's handle-keyed hash maps with the standard library's mutable
SortedMap, giving component-task, waitable-subscriber, and prepared future/stream producer registries logarithmic lookup, insertion, and removal without depending on hash distribution.The change preserves the existing registration and removal points, including removing producer entries before starting bridges or running cleanup. Generated packages import
moonbitlang/core/sorted_maponly when they emit producer tables; external imports share the existing alias namespace to prevent collisions.This is an independent follow-up to #1742 so the resource ownership changes can land separately. Public WIT map types, resource representations, coroutine membership sets, and CI configuration retain their existing behavior. The collection comes from the standard library and adds no third-party dependency.