Fix compiler warnings - #134
Merged
Merged
Conversation
bobzhang
marked this pull request as ready for review
July 14, 2026 14:28
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.
Summary
try?captures with explicitResultconstruction where the result must escapeWhy
The latest MoonBit compiler reports 32 warnings for syntax and APIs that have become deprecated or ambiguous. These warnings make routine checks noisy and risk turning into future build failures.
Impact
Builds are warning-free across all supported targets. Error-to-property conversion behavior is preserved, and generated public interfaces are unchanged.
Validation
moon check --target all --warn-list +unnecessary_annotation --deny-warn --diagnostic-limit 1000moon test --target all --warn-list +unnecessary_annotation --diagnostic-limit 1000(304 tests passed on each target)moon fmtmoon info(no public API diff)