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
Ah, so a crate can export both, but the crate that contains the proc macro cannot export anything else? As it's currently setup, askama_derive depends on askama, but I guess circular dependencies are not supported, right?
I would prefer to drop the dependency of askama_derive on askama by moving the codegen-related code into the derive crate. Then you can re-export the derive from askama and save users the trouble of depending on two crates.
Yeah, that would be much nicer. It was how I set it up initially, but since I misunderstood the exporting restrictions figured that it made more sense to put all the logic together.
They can actually. If you are okay requiring Rust >=1.15 to compile askama, you can include this in askama/src/lib.rs:
Then users can write:
and get access to the derives that way.
The text was updated successfully, but these errors were encountered: