Repository navigation
Conversation
…at-20261030 # Conflicts: # lib/memory.wasm.mbt # lib/moon.pkg
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.
The current prerelease warns on legacy operator declarations and implicit promoted methods. Use explicit indexing aliases and Eq/Default extensions, then refresh formatting and the generated interface.
This branch also incorporates the existing #4 fork commits with author history preserved, resolving conflicts against current main: retain the current JS/GC export configuration, select backend-specific files explicitly, and use the current Wasm decrement primitive. #4 itself is unchanged.
Validated with moon 0.1.20261029 / moonc v0.10.19+74b7643b8: strict JS and Wasm GC checks, release builds for JS/Wasm GC/Wasm, and 8,991 CPU states and cycle counters against nestest.log on both JS and GC. Target-specific moon info and moon fmt --check pass. The repository has no native audio/video FFI, so all-target info fails on native and is not claimed as passing. Existing backend-specific public exports remain different by design.