Alisa Feistel

- Only `FfiWakerBase` is used by vtable functions (as it's the stable ABI) - In general, the pointer isn't guaranteed to (and is expected, at times, not to) point to...

Different `waker_vtable` addresses for same type

4

```rs use futures::task::ArcWake; struct Temp; impl ArcWake for Temp { fn wake_by_ref(arc_self: &std::sync::Arc) { let _ = arc_self; } } fn main() { let temp = std::sync::Arc::new(Temp); let waker =...

Similar patch (by, if I understand correctly, forcing these to be in the same CGUs) to https://github.com/rust-lang/rust/pull/121622

Task wakes too often in release mode when used with `async_std`

14

This may cause a CPU core to be constantly at `100%` after a client connects and sends nothing: ```rs #[async_std::main] async fn main() -> async_tungstenite::tungstenite::Result { let listener = async_std::net::TcpListener::bind("127.0.0.1:8080").await?;...

Clippy recently(-ish) stabilised a new lint, and code generated by `#[sabi_trait]` seems to fail it. From recursive macro expansion: ```rs #[doc = r""] pub obj: Broker_Backend, ```

An attempt to make `clippy` and `rustc` complain less

1

Submitting this as a draft PR, since there are somewhat many changes (I doubt anyone would be willing to review them all at once — I'll probably make separate PRs for each...

stabby

3

`abi_stable` seems to have been abandoned ~~I don't yet know what the implications of this are in terms of how `stabby` lays stuff out in memory (especially `enum`s)~~ (nvm, checked,...

## What did you implement: Replaces `Result` with `std::result::Result` in the derived code. Why: had errors because of `type Result = std::result::Result` (a common thing to do). We really should...