Skip to content

Remove old fixed length vector syntax #3664

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Oct 5, 2012 · 2 comments
Closed

Remove old fixed length vector syntax #3664

brson opened this issue Oct 5, 2012 · 2 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
0.5

Comments

@brson
Copy link
Contributor

brson commented Oct 5, 2012

Hot:

let foo: [bar * 2] = [baz, quux];

Not:

let foo: [bar]/2 = [baz, quux]/_;
@bstrie bstrie mentioned this issue Oct 12, 2012
Closed
@lucab
Copy link
Contributor

lucab commented Nov 3, 2012

As the pull request is closed, maybe also this issue should too...

@catamorphism
Copy link
Contributor

Thanks!

bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
@bors
Auto merge of rust-lang#5061 - ThibsG:UselessMatch3664, r=flip1995
298df70 
Add new lint: match with a single binding statement

This lint catches `match` statements that binds to only one block and could be rewritten using a simple `let` statement.

Lint name: MATCH_SINGLE_BINDING

fixes: rust-lang#3664

changelog: add lint for match with single binding statement
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@calebcartwright @topecongiro
fix: handling of --all when dep name and dir name differ (rust-lang#3664
ff49b80 
)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
0.5
Development

No branches or pull requests
3 participants
@lucab @brson @catamorphism