Tamika Nomara

I'm building on top of `mockall` and ran into the very same issue. Definitely would like to see a `Predicate` for tuples of predicates.

If I understand this correctly, `IntoBoxPredicate` is just a workaround for orphan rule. Upstream crate can definitely implement `Predicate` for tuples of predicates directly. Alternatively, we can have a function...

I suppose I'd use it the same way it is used by the generated code. I.e., my struct that represents mocked contract will have `in_sequence` method, which takes a `Sequence`,...

Sorry, was away for some time. Here's an example of our crate's API when used with sequences: https://github.com/gnosis/ethcontract-rs/blob/main/ethcontract-mock/src/test/mod.rs#L118 Specifically, we save mockall's sequence [in our code][1], then we [verify and...

I mean, not exactly. I've manually implemented the same code for smart contracts that mockall would generate for traits and structs. Thus, it uses this semi-public API for generated code....

Yes, that's exactly what I'm doing.

Idea from #512: Implement `ArtifactBuilder` to build all/some contracts from an artifact.

I'm not sure if it works with `build.rs`, but with macros it certainly isn't the case.

So it looks like we can't add dependency on actual JSON files unless we `include!` them 😕

Yes, the optimizer will remove the data. However, the compiler will still read that data and include it into AST (at least HIR, not sure about MIR). This will potentially...