Skip to content

Ignore another error during WIT generation #2213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 2, 2025

Conversation

alexcrichton
Copy link
Member

This commit ignores errors generating documents such as:

world a {
    @unstable(...)
    import foo;
}

world b {
    include a;
    @stable(...)
    import foo;
}

This is relatively difficult to prevent so instead let's just throw out the test case.

This commit ignores errors generating documents such as:

    world a {
        @unstable(...)
        import foo;
    }

    world b {
        include a;
        @stable(...)
        import foo;
    }

This is relatively difficult to prevent so instead let's just throw out
the test case.
@alexcrichton alexcrichton requested a review from a team as a code owner June 2, 2025 14:55
@alexcrichton alexcrichton requested review from dicej and removed request for a team June 2, 2025 14:55
Some new warnings cropping up to handle.
@alexcrichton alexcrichton added this pull request to the merge queue Jun 2, 2025
Merged via the queue into bytecodealliance:main with commit a523f31 Jun 2, 2025
32 checks passed
@alexcrichton alexcrichton deleted the fix-a-fuzz-case branch June 2, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants