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

use PathBuf in cargo metadata #6511

Merged
merged 2 commits into from
Jan 2, 2019
Merged

use PathBuf in cargo metadata #6511

merged 2 commits into from
Jan 2, 2019

Conversation

matklad
Copy link
Member

@matklad matklad commented Jan 2, 2019

I don't remember why we've used strings in the first place here, but I
think that historically there just weren't Serialize impls for
Paths!

I don't remember why we've used strings in the first place here, but I
think that historically there just weren't Serialize impls for
`Path`s!
@rust-highfive
Copy link

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@dwijnand
Copy link
Member

dwijnand commented Jan 2, 2019

I wondered if it's to avoid unlocked path usage (as opposed to Filesystem), but I see these are all types designed for serialisation, so LGTM!

@bors: r

@bors
Copy link
Collaborator

bors commented Jan 2, 2019

📌 Commit 52810dd has been approved by dwijnand

@bors
Copy link
Collaborator

bors commented Jan 2, 2019

⌛ Testing commit 52810dd with merge 4dc7e36...

bors added a commit that referenced this pull request Jan 2, 2019
use PathBuf in cargo metadata

I don't remember why we've used strings in the first place here, but I
think that historically there just weren't Serialize impls for
`Path`s!
@bors
Copy link
Collaborator

bors commented Jan 2, 2019

☀️ Test successful - status-appveyor, status-travis
Approved by: dwijnand
Pushing 4dc7e36 to master...

@bors bors merged commit 52810dd into rust-lang:master Jan 2, 2019
bors added a commit that referenced this pull request Jan 2, 2019
serialize version directly

Streamline serialization more, cc #6511
bors added a commit to rust-lang/rust that referenced this pull request Jan 4, 2019
Update cargo

24 commits in 0d1f1bbeabd5b43a7f3ecfa16540af8e76d5efb4..34320d212dca8cd27d06ce93c16c6151f46fcf2e
2018-12-19 14:45:14  0000 to 2019-01-03 19:12:38  0000
- Display environment variables for rustc commands (rust-lang/cargo#6492)
- Fix a very minor race condition in `cargo fix`. (rust-lang/cargo#6515)
- Add a high-level overview of how `fix` works. (rust-lang/cargo#6516)
- Add dependency `registry` to `cargo metadata`. (rust-lang/cargo#6500)
- Fix fingerprint calculation for patched deps. (rust-lang/cargo#6493)
- serialize version directly (rust-lang/cargo#6512)
- use DYLD_FALLBACK_LIBRARY_PATH for dylib_path_envvar on macOS (rust-lang/cargo#6355)
- Fix error message when resolving dependencies (rust-lang/cargo#6510)
- use PathBuf in cargo metadata (rust-lang/cargo#6511)
- Fixed link to testsuite in CONTRIBUTING.md (rust-lang/cargo#6506)
- Update display of contents of Cargo.toml (rust-lang/cargo#6501)
- Update display of contents of Cargo.toml (rust-lang/cargo#6502)
- Fixup cargo install's help message (rust-lang/cargo#6495)
- testsuite: Require failing commands to check output. (rust-lang/cargo#6497)
- Delete unnecessary 'return' (rust-lang/cargo#6496)
- Fix new unused patch warning. (rust-lang/cargo#6494)
- Some minor documentation changes. (rust-lang/cargo#6481)
- Add `links` to `cargo metadata`. (rust-lang/cargo#6480)
- Salvaged semver work (rust-lang/cargo#6476)
- Warn on unused patches. (rust-lang/cargo#6470)
- don't write a an incorrect rustc version to the fingerprint file (rust-lang/cargo#6473)
- Rewrite `login` and registry cleanups. (rust-lang/cargo#6466)
- [issue#6461] Fix cargo commands list (rust-lang/cargo#6462)
- Restrict registry names to same style as package names. (rust-lang/cargo#6469)
@ehuss ehuss added this to the 1.33.0 milestone Feb 6, 2022
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.

6 participants