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

Explicitly declare [lib] and [[bin]] targets for forc #1174

Merged
merged 1 commit into from
Apr 7, 2022

Conversation

mitchmindtree
Copy link
Contributor

This allows to remove some duplication between the lib.rs and
main.rs modules, and should allow us to remove the catch-all
#![allow(dead_code)] attribute in lib.rs in a follow-up PR.

This allows to remove some duplication between the `lib.rs` and
`main.rs` modules, and should allow us to remove the catch-all
`#![allow(dead_code)]` attributes.
@mitchmindtree mitchmindtree merged commit 085c7c1 into master Apr 7, 2022
@mitchmindtree mitchmindtree deleted the mitchmindtree/forc-lib-bin branch April 7, 2022 00:34
mitchmindtree added a commit that referenced this pull request Apr 7, 2022
This was originally required in order to support the separate implicit
`bin` and `lib` targets for `forc` without getting loads of warnings,
but as of #1174 `cargo` is aware of the separate targets and this is no
longer necessary.
mitchmindtree added a commit that referenced this pull request Apr 7, 2022
This was originally required in order to support the separate implicit
`bin` and `lib` targets for `forc` without getting loads of warnings,
but as of #1174 `cargo` is aware of the separate targets and this is no
longer necessary.
mitchmindtree added a commit that referenced this pull request Apr 7, 2022
* Remove `#![allow(dead_code)]` from `forc` along with dead code

This was originally required in order to support the separate implicit
`bin` and `lib` targets for `forc` without getting loads of warnings,
but as of #1174 `cargo` is aware of the separate targets and this is no
longer necessary.

* Remove old feature-gated start_fuel_core re-export
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants