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
Figure out limitations to this approach. Will it scale with async for example
Where should the __generated fn be placed? Is it good enough to put it in the module, or, especially for custom macro's, do we want the implementation to be stacked inside the #[maybe_my_custom_test] fn?
Can we replace the current binding based implementation completely? Or do we want or need to keep both?
#[parameterized(a = {0}, b = {1})]fnnumbers<T:Into<u8>>(input:T){assert_eq!(0, input)}mod test {#[test]fna(){fn__generated<T:Into<u8>>(input:T){assert_eq!(0, input.into());}__generated(0);}#[test]fnb(){fn__generated<T:Into<u8>>(input:T){assert_eq!(0, input.into());}__generated(1);}}
Can we replace the current binding based implementation completely? Or do we want or need to keep both?
and
The text was updated successfully, but these errors were encountered: