tree 98c5e8b17dcc14b4dcd77227c32f285c7550b49d
parent 6c448b26dd4f22f16c2b23e224d611c94f690a00
author yanok <yanok@google.com> 1682506536 +0000
committer Ilya Yanok <ilya.yanok@gmail.com> 1682542040 +0200

Fix the type variable capture problem

Consider this example:

```dart
class Foo<E> {
  Iterable<T> map(T Function(E) f) => /* ... */
}

class Bar<T> extends Foo<T> {}

@GenerateNiceMocks([MockSpec<Bar>])
void main() {}
```

When generating an override for `map` we just use an `element.name` String to generate types, so we end up with this:

```dart
Iterable<T> map(T Function(T) f)
```

These must be two different `T`s, one bound at the class definition while another one at the method definition. But since we converted
them to strings, we lost this information, so now they all refer to the `T` bound by the method declaration.

Ideally I'd like code_builder to handle this for us, but there are no signs of any type variable support, so I thought it should be pretty straight forward to add it on Mockito level. We just need to check if we are shadowing any existing type variable while adding a new one and rename the new one if that's the case.

PiperOrigin-RevId: 527221562