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

rustpkg: Build dependencies into the correct workspace when using --rust-path-hack #10110

Merged
merged 1 commit into from
Oct 28, 2013

Conversation

catamorphism
Copy link
Contributor

r? @metajack When invoked with the --rust-path-hack flag, rustpkg was correctly building
the package into the default workspace (and not into the build/ subdirectory of the
parent directory of the source directory), but not correctly putting the output
for any dependencies into the default workspace as well.

Spotted by Jack.

…ust-path-hack

When invoked with the --rust-path-hack flag, rustpkg was correctly building
the package into the default workspace (and not into the build/ subdirectory of the
parent directory of the source directory), but not correctly putting the output
for any dependencies into the default workspace as well.

Spotted by Jack.
bors added a commit that referenced this pull request Oct 28, 2013
…, r=metajack

r? @metajack When invoked with the --rust-path-hack flag, rustpkg was correctly building
the package into the default workspace (and not into the build/ subdirectory of the
parent directory of the source directory), but not correctly putting the output
for any dependencies into the default workspace as well.

Spotted by Jack.
@bors bors closed this Oct 28, 2013
@bors bors merged commit 0e6a575 into rust-lang:master Oct 28, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 12, 2023
…exendoo

Fix FN in `needless_return`

Fixes rust-lang#10051

changelog: Enhancement: [`needless_return`]: Now detects more cases for returns of owned values
[rust-lang#10110](rust-lang/rust-clippy#10110)
<!-- changelog_checked -->
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.

4 participants