You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
It would be cool if syntex could be taught about some of the common built-in macros. For example, if println! and vec! were "expanded" to be themselves, but syntex was made aware that they accepted a list of expressions as arguments, and that the expressions should be expanded as usual. I'll admit that I don't know exactly in the tree where that change would have to be made, so I don't know how hard it would be to get that to work without significant changes to syntex_syntax.
A much more complex, but also cool, thing would be to also support macro_rules! expansion within syntex. This would mean that if enough built-in macros were used, and no compiler plugins were used, syntex could theoretically be used to expand almost any macro tree. I don't think this is a good idea for complexity reasons, but it would be cool at least :).
The text was updated successfully, but these errors were encountered:
It would be cool if syntex could be taught about some of the common built-in macros. For example, if
println!
andvec!
were "expanded" to be themselves, but syntex was made aware that they accepted a list of expressions as arguments, and that the expressions should be expanded as usual. I'll admit that I don't know exactly in the tree where that change would have to be made, so I don't know how hard it would be to get that to work without significant changes to syntex_syntax.A much more complex, but also cool, thing would be to also support macro_rules! expansion within syntex. This would mean that if enough built-in macros were used, and no compiler plugins were used, syntex could theoretically be used to expand almost any macro tree. I don't think this is a good idea for complexity reasons, but it would be cool at least :).
The text was updated successfully, but these errors were encountered: