Skip to content
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

Fix issue 9410 by removing special-case hack to suppress unknown attribute warnings on aptos_stdlib #10167

Closed
wants to merge 0 commits into from

Conversation

brmataptos
Copy link
Contributor

@brmataptos brmataptos commented Sep 21, 2023

Description

PR 9229 introduced warnings on unknown attributes, but suppressed them for aptos_stdlib to avoid user consternation about problems in the Aptos codebase. It also removed those attributes from the codebase, so now that it is released it becomes safe to Fix issue 9410 and remove the special-case for the aptos_stdlib.

Test Plan

Existing test cases, new test outputs.

Copy link
Contributor

@vineethk vineethk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm.

┌─ tests/move_check/parser/aptos_stdlib_attributes.move:7:7
7 │ #[testonly]
│ ^^^^^^^^ Attribute name 'testonly' is unknown (use --skip-attribute-checks CLI option to ignore); known attributes are '{"bytecode_instruction", "deprecated", "expected_failure", "native_interface", "test", "test_only", "verify_only"}'.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a comment for this PR, but this seems like a good candidate for the move linter (to identify the closest allowed attribute and suggest it as fix).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, there is a list displayed. Good point, though.

@brmataptos
Copy link
Contributor Author

Note this PR was defective (was on my main instead of a branch), so I've closed it and am reopening as #10175.

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