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

Method-ify CStore #11146

Merged
merged 2 commits into from
Dec 26, 2013
Merged

Method-ify CStore #11146

merged 2 commits into from
Dec 26, 2013

Conversation

sfackler
Copy link
Member

I also deleted a test which has apparently not been needed for a very long time.

The associated issue has been closed for 2 years!
bors added a commit that referenced this pull request Dec 26, 2013
I also deleted a test which has apparently not been needed for a very long time.
@bors bors closed this Dec 26, 2013
@bors bors merged commit c7cf5dc into rust-lang:master Dec 26, 2013
@emberian
Copy link
Member

Woo cleanup!

@sfackler sfackler deleted the cleanup branch May 15, 2014 05:03
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 14, 2023
…, r=Centri3,xFrednet

[`tuple_array_conversions`]: move from `complexity` to `nursery`

The lint suggestion is arguably often less readable and more complex than the original code.

For example, which of the following is the most readable:
```rust
let _vertices = edges.flat_map(|(src, dst)| [src, dst]);
let _vertices = edges.flat_map(<_ as Into<[i32; 2]>>::into);
let _vertices = edges.flat_map(<[i32; 2]>::from);
```

The lint can be useful, but really only applies if the tuple is either long enough that naming the fields is silly (maybe at least 4 entries long), or if the author intends the fields to be homogenous, which is author intent and can't be determined by the lint. Therefore I think the lint should be marked as pedantic.

Currently, there are also a lot of false positives with the lint:
* rust-lang/rust-clippy#11082
* rust-lang/rust-clippy#11085
* rust-lang/rust-clippy#11100 (rust-lang/rust-clippy#11105)
* rust-lang/rust-clippy#11124
* rust-lang/rust-clippy#11144

Should fix those issues before enabling it for everyone.

---

changelog: Move [`tuple_array_conversions`] to `nursery` (Now allow-by-default)
<!-- FIY: Ignore this change, if the commit gets backported -->
[rust-lang#11146](rust-lang/rust-clippy#11146)
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 31, 2023
…sery, r=xFrednet

Move tuple_array_conversions to nursery

changelog: Move [`tuple_array_conversions`] to `nursery` (Now allow-by-default)
<!-- FIY: Ignore this change, if the commit gets backported and also rust-lang/rust-clippy#11146 -->
[rust-lang#11172](rust-lang/rust-clippy#11172)

The nursery change got lost in rust-lang#11146 and it ended up in pedantic, this puts it in nursery and gives something to backport

r? `@xFrednet`
flip1995 pushed a commit to flip1995/rust that referenced this pull request Aug 17, 2023
…sery, r=xFrednet

Move tuple_array_conversions to nursery

changelog: Move [`tuple_array_conversions`] to `nursery` (Now allow-by-default)
<!-- FIY: Ignore this change, if the commit gets backported and also rust-lang/rust-clippy#11146 -->
[rust-lang#11172](rust-lang/rust-clippy#11172)

The nursery change got lost in rust-lang#11146 and it ended up in pedantic, this puts it in nursery and gives something to backport

r? `@xFrednet`
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