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

Add an INSTALL.txt #1621

Merged
merged 1 commit into from
Jan 23, 2012
Merged

Add an INSTALL.txt #1621

merged 1 commit into from
Jan 23, 2012

Conversation

thoughtpolice
Copy link
Contributor

The installation procedure requires internet anyway, but some Unix denizens may be a little muffed at the idea a source package doesn't contain installation instructions! This is basically a slightly modified copy of the installation instructions in the tutorial.

Note, the windows bit is currently commented out as a FIXME, since the installer is broken. The link to the installer should be taken out of the tutorial as well - I'll submit a request for that shortly.

When Rust 0.2 or 1.0 or whatever comes out, this should be part of the distributed tarball. So it'll need to be added to the distribution. I can also do this.

@thoughtpolice
Copy link
Contributor Author

The latest fix in this commit makes INSTALL.txt part of the source distribution as well.

brson added a commit that referenced this pull request Jan 23, 2012
@brson brson merged commit afc3abc into rust-lang:master Jan 23, 2012
flip1995 added a commit to flip1995/rust that referenced this pull request Aug 11, 2020
…ord-lint, r=matthiaskrgr

Add derive_ord_xor_partial_ord lint

Fix rust-lang#1621

Some remarks:
This PR follows the example of the analogous derive_hash_xor_partial_eq lint where possible.
I initially tried using the `match_path` function to identify `Ord` implementation like the derive_hash_xor_partial_eq lint currently does, for `Hash` implementations but that didn't work.

Specifically, the structs at the top level were getting paths that matched `&["$crate", "cmp", "Ord"]` instead of `&["std", "cmp", "Ord"]`. While trying to figure out what to do instead I saw the comment at the top of [clippy_lints/src/utils/paths.rs](https://github.com/rust-lang/rust-clippy/blob/f5d429cd762423901f946abd800dc2cd91366ccf/clippy_lints/src/utils/paths.rs#L5) that mentioned [this issue](rust-lang/rust-clippy#5393) and suggested to use diagnostic items instead of hardcoded paths whenever possible. I looked for a way to identify `Ord` implementations with diagnostic items, but (possibly because this was the first time I had heard of diagnostic items,) I was unable to find one.

Eventually I tried using `get_trait_def_id` and comparing `DefId` values directly and that seems to work as expected. Maybe there's a better approach however?

changelog: new lint: derive_ord_xor_partial_ord
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