Matt Corallo 70440a529e [bindings] Use consistent imports for MessageSendEvents traits ... Our bindings generator is braindead with respect to the idents used in a trait definition - it treats them as if they were used where the trait is being used, instead of where the trait is defined. Thus, if the idents used in a trait definition are not also imported the same in the files where the traits are used, we will claim the idents are bogus. I spent some time trying to track the TypeResolvers globally through the entire conversion run so that we could use the original file's TypeResolver later when using the trait, but it is somewhat of a lifetime mess. While likely possible, import consistency is generally the case anyway, so unless it becomes more of an issue in the future, it likely makes the most sense to just keep imports consistent. This commit keeps imports consistent across trait definition files around `MessageSendEvent` and `MessageSendEventsProvider`.		2021-02-01 16:52:57 -05:00
..
src	[bindings] Use consistent imports for MessageSendEvents traits	2021-02-01 16:52:57 -05:00
Cargo.toml	Expose test_utils to fuzztarget (in addition to _test_utils feature)	2021-01-04 12:40:40 -05:00