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

Add [ to the follow set for ty #31135

Closed
nikomatsakis opened this issue Jan 22, 2016 · 2 comments
Closed

Add [ to the follow set for ty #31135

nikomatsakis opened this issue Jan 22, 2016 · 2 comments
Assignees
Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@nikomatsakis
Copy link
Contributor

As decided in rust-lang/rfcs#1462.

cc @pnkfelix
cc @retep998

@nikomatsakis nikomatsakis added A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 22, 2016
@durka
Copy link
Contributor

durka commented Jan 23, 2016

So according to the RFC document, FOLLOW(path) = FOLLOW(ty). Does that mean we are adding [ to FOLLOW(path) as well? (My assumption is no.)

@nikomatsakis
Copy link
Contributor Author

Seems like yes. After all, a type can be just a path, so if we added a
[ suffix on paths, it would effectively add such a suffix to types
as well.

On Sat, Jan 23, 2016 at 09:20:33AM -0800, Alex Burka wrote:

So according to the RFC document, FOLLOW(path) = FOLLOW(ty). Does that mean we are adding [ to FOLLOW(path) as well?


Reply to this email directly or view it on GitHub:
#31135 (comment)

@bors bors closed this as completed in e1e0de8 Jan 26, 2016
pnkfelix pushed a commit to pnkfelix/rust that referenced this issue Feb 5, 2016
Following RFC 1462 (amending 550). Closes rust-lang#31135.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants