Skip to content

Conversation

@mpetrov
Copy link
Contributor

@mpetrov mpetrov commented Aug 16, 2019

Type ambiguities can arise if the proto module mappings are not factored
in. For example, if a message named Version is defined in a separate
module, and used in a unary call the generated generic arguments
ClientCallUnaryBase<Version, Version> are ambiguous:

SwiftProtobuf.Version:1:15: note: found this candidate
public struct Version {
              ^
some_module.Version:1:15: note: found this candidate
public struct Version {

Type ambiguities can arise if the proto module mappings are not factored
in. For example, if a message named `Version` is defined in a separate
module, and used in a unary call the generated generic arguments
`ClientCallUnaryBase<Version, Version>` are ambiguous:

```
SwiftProtobuf.Version:1:15: note: found this candidate
public struct Version {
              ^
some_module.Version:1:15: note: found this candidate
public struct Version {
```
@MrMage
Copy link
Collaborator

MrMage commented Aug 16, 2019

Thank you for the cherry-pick! Will merge the other PR once the CI re-run has succeeded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants