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

(cargo) fixed a package installation bug, cleaned up usage #2454

Merged
merged 3 commits into from
May 29, 2012

Conversation

killerswan
Copy link
Contributor

This fixes a bug where os::copy_file was called with a directory name, and
updates the command line options and usage messages for clarity.

This fixes a bug where os::copy_file was called with a directory name, and
updates the command line options and usage messages for clarity.
Since `os::copy_file` wasn't preserving the executable permissions,
this reverts back to `run::run_program` and `cp` to install
the packages.
erickt added a commit that referenced this pull request May 29, 2012
(cargo) fixed a package installation bug, cleaned up usage
@erickt erickt merged commit 07db8c8 into rust-lang:master May 29, 2012
@erickt
Copy link
Contributor

erickt commented May 29, 2012

Thanks!

bors added a commit to rust-lang-ci/rust that referenced this pull request Sep 22, 2022
Improve information sharing across SB diagnostics

Previous Stacked Borrows diagnostics were missing a lot of information about the state of the interpreter, and it was difficult to add additional state because it was threaded through all the intervening function signatures.

This change factors a lot of the arguments which used to be passed individually to many stacked borrows functions into a single `DiagnosticCx`, which is built in `Stacks::for_each`, and since it wraps a handle to `AllocHistory`, we can now handle more nuanced things like heterogeneous borrow of `!Freeze` types.
celinval added a commit to celinval/rust-dev that referenced this pull request Jun 4, 2024
This fixes a regression from rust-lang#2439. The compiler should store the location of the function body instead of the declaration. Storing the correct location fixes how concrete playback stores the generated unit test.
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