experiment: add a new method to core using stable functions #5551
Conversation
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
…ng change and requires not just a migration, but a migration that holds on to both old and new core library.
crusso
commented
Oct 6, 2025
| }; | ||
|
|
||
| // some new method | ||
| public func copy() : Map<K,V> { |
There was a problem hiding this comment.
This is the only difference between core1 and core0 (a new copy method)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a simple example demonstrating that just adding method to core (Map.copy) is a breaking change
and requires not just a migration, but a complex migration that holds on to both old and new core library.