Skip to content

Rustpkg: tests, and doing inference properly #5920

New issue

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

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

Already on GitHub? # to your account

Closed
wants to merge 9 commits into from

Conversation

catamorphism
Copy link
Contributor

1. Fail when there's no package script and no crates named
main.rs, lib.rs, bench.rs, or test.rs.

2. Inject the crate link_meta "name" and "vers" attributes, so
that the output file gets named correctly in the library case.

3. Normalize '-' to '_' in package names.
There's no test runner for rustpkg yet; just sketching out a few
basic test scenarios. pass/ contains packages that should compile
successfully, whereas fail/ contains packages that should fail
to build.
1. Implemented the `clean` command

2. The methods implementing rustpkg commands all returned `bool`.
Since most of not all of the error situations seem unrecoverable,
I changed the methods to return unit (and also stubbed out several
more methods that were assuming a package script existed, to be
re-implemented in the future)
This is a test file containing examples of commands that should
succeed. When we write the test runner, we will have to figure
out how to automate them.
These are examples of what *should* work, and probably don't
work yet.
@bors bors closed this Apr 18, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Aug 28, 2020
…_call, r=mikerite

Fix FP for `redundant_closure_call`

Fix rust-lang#5916

changelog: Fix FP for `redundant_closure_call` when called in function body
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants