I have a codebase with the same logic (to get a Vector of bytes) copy-pasted repeatedly:

I want to create a mechanism that ensures resources are released, similar to how we can use drop. However I want to enforce more complex constraints using Rust’s type system. I would like to ensure that the user satisfies some constraints before they can drop their object. One way we could with files is we could have a type File<T: ResourceState> with

I’m trying to implement a typestate system that is generic over its implementation/implementer. For a minimal reproduction, consider 2 states under State:

I’ve been messing a lot with Rust type system, and I’ve always hit the same barrier, the fact that we can’t tell if two types are the same at compile time. More precisely, the fact that two types are different.

I’m curious what the difference is between execute(&mut *transaction) and execute(&mut transaction) in my example since I didn’t think that transaction was a pointer to begin with but for some reason execute(&mut *transaction) satisfies the trait point while execute(&mut transaction) does not.

I am using the tiberius crate for MSSQL Queries in Rust.