Linus Färnstrand

We can word it differently and maybe skip the example. But I feel it would be good if the guidelines touched on this topic in general. If we agree it's...

By "context" to you mean to have the error return the source error from its "Error::source" implementation? I think errors should return the error that caused them where relevant, yes....

> The problem is that the Error trait has only recently evolved to a point where this sort of API guideline is actually reasonable. I don't think I understand. `Error::cause`...

**Alternative solution:** Deprecate `source` and make the guideline be to fully explain an error (including its source) in the `Display` impl. IMO that's even better. I have never understood the...

My takeaway is that we first need to figure out what the preferred way of **using** errors is, before we know the best way to design them. * How should...

Maybe you mean something different than what I experience. But I get false negatives due to this. If I run `cargo udeps --all-targets` on Linux, in a crate with: ```toml...

Can you be a *little* bit more descriptive? 😅

It could be implemented for only the platforms that supports it natively and ignoring Windows. By a `unix` extension trait: `midir::os::unix::MidiOutputConnectionExt` that has `MidiOutputConnectionExt::send_at` and takes the extra parameter being...

Sorry. I searched the history for "trait" only, so I missed it. Most of the thread was about how to implement the scheduling so I did not read every message.

:heart::crab::heart: