Update API trait with GAT

[drmingdrmer]

https://blog.rust-lang.org/2022/11/03/Rust-1.65.0.html#whats-in-1650-stable

[github-actions]

👋 Thanks for opening this issue!

Get help or engage by:

• /help : to print help messages.
• /assignme : to assign this issue to you.

[Xuanwo]

Hi, this issue has been open for a while. Perhaps we can schedule some actionable tasks to get it started?

[schreter]

In fact, in the meantime we can simply use async functions in traits (since 1.75). For single-threaded mode, the add_async_trait macro is a no-op and we are using native async fn in trait. @wvwwvwwv implemented that.

For "regular" use, I think there were some concerns regarding Send-ability of the generated futures. But you may try to simply remove async_trait completely and see what happens. If it "simply works" then it would be the best.

[schreter]

@Xuanwo Ah, I just see there is a PR #996 which addresses this by specifying Send bounds as needed. So this issue is then moot, we should merge that (provided it works, of course - but it seems like it does :-) and with that #959 is completely done. I.e., this is in a way duplicate of #959 .

[drmingdrmer]

Dup of:

• Ditch async_trait in favor of the official async_fn_in_trait feature #959

Fixed in:

• Change: #959 ditch async_trait for the singlethreade feature #982
• Change: replace async_trait with RPITIT #996