nvksv / maybe-async-cfg Goto Github PK

Right now, the only option for async and sync to coexist at the same time is to rename one or both of them to have Sync / Async suffixes. I think the ergonomics would be much better if you could use a module instead. E.g.:

#[maybe_async_cfg::maybe(sync(keep_self), async(feature="async",self="async"))]
pub mod blocking {
  pub async fn hello_world() {
    "Hellorld"
  }
}

which would expand to

pub mod blocking {
  pub fn hello_world() {
    "Hellorld"
  }
}
pub mod async {
  pub async fn hello_world() {
    "Hellorld"
  }
}

and thereby make the two versions differ only by which module is use'd.

Bonus points if you could have one of the branches omit the mod entirely to put the symbols in the parent module, as a way of migrating existing blocking-only crates.