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.
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
Add
no_main
lint #2001Add
no_main
lint #2001Changes from 6 commits
e5635b9
aebee32
4033d24
34f236d
3a4955c
05b3a42
c977fa6
bbec165
a1f87d9
7b237d3
3e17b24
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we execute this lint on all the builds, even for e2e tests, making
no_main
mandatory for every ink! contract?The point is that
cargo-contract
always runs linter for the host architecture. It is possible to hack it a bit, but should we? Why should we skip this lint for tests?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E2E tests will still run the linter because they compile the contract code blob.
Maybe what we really mean/want is that when building the contract "natively" i.e. not
no_std
, which happens for unit tests and metadata generation. But those are usually executed on a different path so maybe we don't need to make the distinction here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I see. Let's try to introduce this lint for all contracts. I think it won't make any problems.