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

Documentation: add an "Is Rust used in production?" FAQ #11511

Closed
kud1ing opened this issue Jan 13, 2014 · 1 comment
Closed

Documentation: add an "Is Rust used in production?" FAQ #11511

kud1ing opened this issue Jan 13, 2014 · 1 comment

Comments

@kud1ing
Copy link

kud1ing commented Jan 13, 2014

Mention

@flaper87
Copy link
Contributor

I expect this list to grow a lot in the future and it's probably better to have it in the website. See Python's example: https://www.python.org/about/success/

steveklabnik added a commit to steveklabnik/rust that referenced this issue Jul 30, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Sep 25, 2023
Split `needless_borrow` into two lints

Splits off the case where the borrow is used as a generic argument to a function. I think the two cases are different  enough to warrant a separate lint.

The tests for the new lint have been reordered to group related parts together. Two warning have been dropped, one looked like it was testing the generic argument form, but it ends up triggering the auto-deref variant. The second was just a redundant test that didn't do anything interesting.

An issue with cycle detection is also included. The old version was checking if a cycle was reachable from a block when it should have been checking if the block is part or a cycle.

As a side note, I'm liking the style of just jamming all the tests into separate scopes in main.

changelog: Split off `needless_borrows_for_generic_args` from `needless_borrow`
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 a pull request may close this issue.

2 participants