Open
Description
Similarly named methods can cause auto-generated method naming conflicts. Specifically if an interface has a naming such as:
Field(string, interface{})
FieldNot(string, interface{})
While charlatan does code generation for Field(), it generates FieldCalled() and FieldNotCalled().
When charlatan attempts to generate methods for FieldNot(), it will generate FieldNotCalled() and draw a method definition naming conflict error, as there is already a FieldNotCalled() method defined by code generation for Field().