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
With rust-lang/rfcs#3698 it would be possible to remove all integration features like with-axum. Instead it would be possible to implement the code generation as a proper macro that is passed as a call-back argument for our generator (untested pseudo-code):
#[doc(hidden)]pubuse{axum_core, rinja};#[macro_export]macro_rules!Template{($($tt:tt)*) => {
$crate::impl_template! {[$($tt)*][$crate::rinja][$crate::impl_integration]// in `rinja` itself this argument would be absent}}}#[doc(hidden)]#[macro_export]macro_rules! impl_integration {([$ident:ident][$($impl_generics:tt)*][$($ty_generics:tt)*]) => {impl $($impl_generics)* $crate::axum_core::response::IntoResponsefor $ident $($ty_generics)*{
#[inline]fn into_response(self) -> $crate::axum_core::response::Response{
$crate::into_response(&self)}}}}
This way --all-features would work fine, and everyone could easily implement their own integration crate.
The text was updated successfully, but these errors were encountered:
With rust-lang/rfcs#3698 it would be possible to remove all integration features like
with-axum
. Instead it would be possible to implement the code generation as a proper macro that is passed as a call-back argument for our generator (untested pseudo-code):This way
--all-features
would work fine, and everyone could easily implement their own integration crate.The text was updated successfully, but these errors were encountered: