FrankReh

Well, I don't want to invoke potential panics - in the code or in the users. The user may choose to call the synchronous close(2) on the raw fd. The...

@thomasbarrett Yes, as in the other issue, I was incorrect thinking close on raw didn't require unsafe code.

How does panicking when there are in flight operations during a drop help? Isn't it better to wait for the in flight operations to finish?

Are you saying the current logic for waiting and then closing is broken? I wish you had referenced - https://github.com/tokio-rs/tokio-uring/issues/122. If that is essentially the same issue, I would have...

@thomasbarrett And the comment you are proposing to add at line 860, "Since all in-flight operations hold a reference to &self". That still isn't right is it? This discussion has...

> Each instantiation should get a unique type `T`, but that can't be reflected in Rust's type system. I only ask because this seems a learning opportunity for people new...

Thank you. You are right that I didn't take the use of `instantiation` correctly. I still have questions about why this part of the API doesn't use the Rust type...

> the R resource has a different type between A1/A2 Is it really a different type, or is it up to the implementation to keep track of which A component...

I was hoping to learn something by looking at this problem. For now, all I can do is confirm the `cargo component build` step from the binary `importer` directory fails,...

I've gotten as far as seeing where the deepest code check is failing. Here a field that is still empty is checked whether it contains the resource name. If I...