Alan Somers
Alan Somers
@ljw1004 your problem is not quite the same, because your only generic parameters are lifetimes. In your case, I think you should be able to simply eliminate the lifetime parameter....
**Update:** I've made some progress on this feature. I have a branch that allows mocking functions with non-static generic parameters, with some restrictions: * You must annotate the function with...
> Hi @asomers , this looks promising. But the solution you provided doesn't work for a generic method with generic return type. > > Please, let me know if I'm...
> Just got bit by this. Wanted to pass a `Drain` iterator into my mocked function but couldn't because of the required 'static bound. Need to allocate a vec to...
> > > Hi @asomers , this looks promising. But the solution you provided doesn't work for a generic method with generic return type. > > > Please, let me...
@TheDan64 sorry I missed this when you posted it. Could you try again, but using mockall's "nightly" feature? That gives much better error messages.
That's because `concretize` creates a trait object under the hood, and Rust imposes some restrictions on what types can be made into trait objects. Try these variations: ```rust #[concretize] fn...
We have a decision to make here. The tradeoff is type safety vs future proofing. The most future-proof way to do this would be to accept any `u32` in `FcntlsBuilder::add`....
Depends on https://github.com/rust-lang/libc/pull/3628
There's nothing that sets `--no-logs-no-support` on the command line. Would anything else cause that output?