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

Move std::num::Integer to libnum #12326

Merged
merged 1 commit into from
Feb 21, 2014
Merged

Move std::num::Integer to libnum #12326

merged 1 commit into from
Feb 21, 2014

Conversation

brendanzab
Copy link
Member

This is part of the effort to simplify std::num, as tracked in issue #10387.

@alexcrichton
Copy link
Member

I'm in favor of this. It seems odd to me for libstd to have both trait Int and trait Integer

@brendanzab
Copy link
Member Author

It made more sense when we had a distinction between Fractional, Real and Float. Now I think we are moving towards a strictly IEEE float trait (see #12281).

@flaper87
Copy link
Contributor

I'm in favor of this change as well. I'm happy to sy std::num being cleaned out.

@alexcrichton
Copy link
Member

Let's do this.

@alexcrichton
Copy link
Member

(as in, with a rebase I'll review and r+)

@brendanzab
Copy link
Member Author

@alexcrichton rebased.

bors added a commit that referenced this pull request Feb 21, 2014
This is part of the effort to simplify `std::num`, as tracked in issue #10387.
@bors bors closed this Feb 21, 2014
@bors bors merged commit 3a9eca3 into rust-lang:master Feb 21, 2014
@brendanzab brendanzab deleted the integer branch February 21, 2014 20:45
@brendanzab
Copy link
Member Author

\o/

bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 25, 2022
…t, r=jonas-schievink

feat: Add "cargo clippy" task preset

We've had a couple of common presets in `Tasks: Run Task -> cargo -> cargo [check,build,test,...]` before. This PR adds `cargo clippy` to that list, which makes for a convenient way of occasionally running Clippy on your code without having to reconfigure the Check on Save command to clippy.

These presets all use the `cargo` task type that we provide, so diagnostics will show up in the editor. However, they don't go through the server-side parsing logic, so it's not possible to apply suggestions, and diagnostics are fairly "low-fidelity". It would be cool if we could somehow pass Cargo's JSON output through the LSP server and render it properly, for arbitrary tasks.

cc rust-lang/rust-analyzer#12323
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