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

parse.expand should use nightly compiler when available like upstream cargo-expand #919

Closed
segevfiner opened this issue Jan 21, 2024 · 1 comment

Comments

@segevfiner
Copy link

parse.expand currently only works on the nightly toolchain, which means this repos test also only work in the nightly toolchain and anyone that wants to use this feature needs to use nightly. Instead, it should use the nightly toolchain when available like upstream cargo-expand does, which will allow it work on stable, with only the expand process using the nightly toolchain.

P.S. Might be nicer to have a way to specify to expand the current crate without listing its name, e.g. expand = true.

Is there any workaround to not use expand if I have some struct generated by a derive macro (e.g. derive_builder) that I want to export?

@emilio
Copy link
Collaborator

emilio commented Apr 14, 2024

We intentionally don't make using nightly-only features easy, that kinda defeats the point of them not being stable. You can achieve what you want with RUSTC_BOOTSTRAP or what not, too, right?

@emilio emilio closed this as completed Apr 14, 2024
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

No branches or pull requests

2 participants