Thanks to visit codestin.com
Credit goes to Github.com

Skip to content

Conversation

@svenpaulsen
Copy link

This includes the minimal necessary updates to get xargo compiling with the latest Rust toolchain. No functional changes were made - just adjustments to ensure compatibility... also applied code formatting using cargo fmt.

@maratik123
Copy link

This fixes #350

Copy link

@bleggett bleggett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, also hit the same error and applied the same fix locally 👍

self.flags.push(home.display().to_string()); // FIXME: we shouldn't use display, we should keep the OsString
// As per CARGO_ENCODED_RUSTFLAGS docs, the separator is `0x1f`.
// As per CARGO_ENCODED_RUSTFLAGS docs, the separator is `0x1f`.
self.flags.join("\x1f")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This formatting change looks semantically wrong. I think the first comment is about home.display()..., but the second one isn't a continuation of it, it's about self.flags.join("\x1f"). The way rustfmt will probably respect the old semantics is by having an empty line between them

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