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

Tracking issue for `quote` feature #29601

Closed
aturon opened this Issue Nov 5, 2015 · 6 comments

Comments

Projects
None yet
5 participants
@aturon
Copy link
Member

aturon commented Nov 5, 2015

Tracks stabilization for the quote_* family of macros.

@eefriedman

This comment has been minimized.

Copy link
Contributor

eefriedman commented Nov 10, 2015

There isn't really much incentive to stabilize this at the moment; this is basically only useful with plugins.

@aturon

This comment has been minimized.

Copy link
Member Author

aturon commented Nov 10, 2015

cc plugin tracking: #29597

@eefriedman Thanks for your help filling out these skeletons! I was a bit uncertain about the right granularity -- we could consolidate some of these plugins-centric features into the plugins tracking issue, perhaps.

@eefriedman

This comment has been minimized.

Copy link
Contributor

eefriedman commented Nov 10, 2015

Mmm... I guess this makes sense to keep separate; we could in theory change the way this feature works, and stabilize it separately from plugins. (For example, we could use some trickery involving duck typing and use statements to allow someone to specify what AST-building library to use.)

@SimonSapin SimonSapin referenced this issue Feb 19, 2017

Open

Tracking issue for 1.0.0 tracking issues #39954

13 of 38 tasks complete
@steveklabnik

This comment has been minimized.

Copy link
Member

steveklabnik commented Mar 8, 2017

Triage: no change

@SimonSapin

This comment has been minimized.

Copy link
Contributor

SimonSapin commented Mar 8, 2017

One change indirectly affecting this is that we now have a concrete plan for Macros 2.0 which will make this feature obsolete, so it is now on a path to (eventual) deprecation rather than stabilization.

@SimonSapin

This comment has been minimized.

Copy link
Contributor

SimonSapin commented Mar 2, 2019

I believe #51285 should have closed this. Please reopen or comment if this is not the case.

@SimonSapin SimonSapin closed this Mar 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.