kangalio

This would be a game-changer, because it would allow you to use cargo-expand to "inline" utility macros like thiserror. Right now a lot of manual effort is required to do...

> This seems possibly helpful for people writing proc-macro's to see how they interact? If the original issue is something you want I'd take a look at it. I'm debugging...

> What exactly does this allow you to do that you can't do without it? Not a whole lot. The code added could go into user crates equally well. If...

> Rust's lifetime system does not know about a closure type that can take ownership of its captures, can execute multiple times, but will never be called concurrently with itself....

I had a look at the source code ([src/backend/alsa/mod.rs](https://github.com/Boddlnagg/midir/blob/c3c435fb44440ca40b45565ac6b91dfcac802428/src/backend/alsa/mod.rs#L264-L280) to be specific) and it seems that a handler thread is spawned for every MidiInputConnection. The callback from MidiInput::connect is moved...

Hi! It's me. Once again I have the opportunity to use your wonderful library, and once again I am thinking about how to get rid of the 'static lifetime in...

I forked midir and made the required modifications in the ALSA backend to remove the 'static constraint on callbacks. It works well and I'm already using the modified version in...

I created the WIP PR as you mentioned: #59. > What if T is borrowed and has a lifetime? Wouldn't that be similar to what you're trying to do? I...

I'll start another attempt with JACK. Maybe I'll figure it out after spending a bit of time reading the code. Also, for clarification regarding your idea with user data; you're...

Look, I managed to fix the JACK backend :) 5683e6d 2 backends done, four to go > The main difference is that you can get the user data back out...