Skip to content

Accept .<> as well as [] for type parameters #468

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
pcwalton opened this issue Jun 10, 2011 · 1 comment
Closed

Accept .<> as well as [] for type parameters #468

pcwalton opened this issue Jun 10, 2011 · 1 comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
0.1 first support...

Comments

@pcwalton
Copy link
Contributor

I think ES4-style option.<int> type parameters have reached consensus. The >> ambiguity should be fixed as well; easiest solution IMO is just to define right shift as two consecutive greater-than signs.
@ghost ghost assigned graydon Jun 27, 2011
@marijnh
Copy link
Contributor

marijnh commented Aug 18, 2011

I guess this is done, with ::<> being used instead.

@marijnh marijnh closed this as completed Aug 18, 2011
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
@ehuss
Merge pull request rust-lang#468 from da-x/literal-matcher-reference
7d85b72 
Mention the literal macro matcher
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@wsmoses
Fix increment usage (rust-lang#468)
702a89f
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@zhassan-aws @tedinski
Fix for computing the minimum offset for an enum variant (rust-lang#468)
6236188
GuillaumeGomez pushed a commit to GuillaumeGomez/rust that referenced this issue Jul 10, 2024
@antoyo
Merge pull request rust-lang#468 from GuillaumeGomez/sync
4720794 
Sync Rust 2024-03-10
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) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
0.1 first supported public release
Development

No branches or pull requests
3 participants
@graydon @marijnh @pcwalton