exposing multiple fields with differing case / underscores causes invalid code generation

[vektah]

Given the schema:

type Foo {
   sizeMapping: [Sizemapping!]!
   size_mapping: [Sizemapping!]! @deprecated
}

The generated complexity struct ends up duplicating a method, which is a compile error:

struct {
        SizeMapping func(childComplexity int) int
        SizeMapping func(childComplexity int) int
}

Worth checking the other field binding logic isn't doing anything too crazy here.

[mathewbyrne]

@vektah this occurs for resolvers (if both fields get a resolver generated) and model gen as well (although I would expect people experiencing this to be with their own models more often). What's the solution here with clashes? I guess some sort of prefix, but it's a little ugly. Perhaps a numeric prefix and an option to specify?