Tait Hoyem

With the hopeful rise of something like `AccessKit`, which should enable Rust programs to talk to native accessibility APIs from different platforms, perhaps the idea of a generic speech interface...

@albertotirla ```rust trait SpeechBackend { ... } impl SpeechBackend for SSIPBackend { ... } impl SpeechBackend for ESpeakBackend { ... } enum SpeechBackendType { SSIPCompatible(SSIPBackend), EspeakNG(ESpeakBackend), } ``` So, only...

> or is espeak considered strictly a fallback backend and it's not to be much configurable since it's for emergency issues only? Exactly.

This would be great! I don't know enough about tts-rs to know if we csn use it with SSML, but generaly I like contributing upsteam, and this seems pretty reasonable.

Does it make sense to abstract away the nature of the mismatch? In my mind, it'd be much more useful to have specific descriptions of the mismatch, instead of having...

Otherwise, this is a welcome change. I'm glad that a rename and redesign was considered.

In the case of `matches_event`, I agree with you. My question is about `try_from_message` which only tells the user that a mismatch occurred, but not why it happened.

Hmmmm.... It looks like this breaks my goal of keeping common WASM compatible. I'm still thinking about this to see if it's strictly necessary, and if it is, how can...

The work is mostly redundant due to #206 Please let me know if I've made a mistake.

Thank you again Luuk for catching these important issues! I really would have never noticed, because I know the history and would have brushed it off. I'm curious why you...