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

Implement RFC 873: Type Macros #27296

Merged
merged 11 commits into from
Aug 6, 2015
Merged

Implement RFC 873: Type Macros #27296

merged 11 commits into from
Aug 6, 2015

Conversation

jroesch
Copy link
Member

@jroesch jroesch commented Jul 26, 2015

This pull request implements the functionality for RFC 873. This is currently just an update of @freebroccolo's branch from January, the corresponding commits are linked in each commit message.

@nikomatsakis and I had talked about updating the macro language to support a lifetime fragment specifier, and it is possible to do that work on this branch as well. If so we can (collectively) talk about it next week during the pre-RustCamp work week.

@rust-highfive
Copy link
Collaborator

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@nikomatsakis
Copy link
Contributor

Can you ad a feature gate (standard procedure)?

@jroesch
Copy link
Member Author

jroesch commented Jul 26, 2015

@nikomatsakis yeah, I wasn't clear about how we were doing RFCs. Feature gate for one release cycle?

("default_type_parameter_fallback", "1.3.0", Active),

// Allows macros to appear in the type position.
("type_macros", "1.3.0", Active)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r-

@huonw
Copy link
Member

huonw commented Jul 30, 2015

Could you add a compile-fail test for the feature gate? And maybe some more basic run-pass tests for the macros themselves?

@bors
Copy link
Contributor

bors commented Jul 31, 2015

☔ The latest upstream changes (presumably #27382) made this pull request unmergeable. Please resolve the merge conflicts.

@jroesch jroesch force-pushed the type-macros branch 3 times, most recently from d6f9311 to 2d80d63 Compare August 1, 2015 23:53
&fld.cx.parse_sess.span_diagnostic,
"type_macros",
t.span,
"type macros are experimental (see tracking issue: 27336)");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think (see issue #27336) is a slightly better phrasing of this.

@huonw
Copy link
Member

huonw commented Aug 3, 2015

r=me with an ERROR in the compile-fail test (and some nits).

@jroesch
Copy link
Member Author

jroesch commented Aug 4, 2015

I addressed all your comments and it should be good to go. @bors r=huonw

@bors
Copy link
Contributor

bors commented Aug 4, 2015

📌 Commit 471370a has been approved by huonw

@bors
Copy link
Contributor

bors commented Aug 5, 2015

⌛ Testing commit 471370a with merge fbf5fcf...

@bors
Copy link
Contributor

bors commented Aug 5, 2015

💔 Test failed - auto-mac-64-nopt-t

@jroesch
Copy link
Member Author

jroesch commented Aug 5, 2015

@bors retry

@jroesch
Copy link
Member Author

jroesch commented Aug 6, 2015

@bors r=huonw

@bors
Copy link
Contributor

bors commented Aug 6, 2015

📌 Commit 83e43bb has been approved by huonw

@bors
Copy link
Contributor

bors commented Aug 6, 2015

⌛ Testing commit 83e43bb with merge 11deb08...

bors added a commit that referenced this pull request Aug 6, 2015
This pull request implements the functionality for [RFC 873](https://github.com/rust-lang/rfcs/blob/master/text/0873-type-macros.md). This is currently just an update of @freebroccolo's branch from January, the corresponding commits are linked in each commit message.

@nikomatsakis and I had talked about updating the macro language to support a lifetime fragment specifier, and it is possible to do that work on this branch as well. If so we can (collectively) talk about it next week during the pre-RustCamp work week.
@bors bors merged commit 83e43bb into rust-lang:master Aug 6, 2015
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.

None yet

5 participants