Fully qualify stdlib types in generated code

[czechboy0]

For example, "any Error" should be "any Swift.Error", and so on.

Some user modules already have conflicting types, and it's difficult to work around this.

[MahdiBM]

@czechboy0 I find it weird that the openapi-generator policy is something in between just use SwiftPM features to solve your problem and the generator should work at all times so we need to fully qualify type names.

I'd be fine with either. Just pointing out that I can't tell when you as the maintainer of the package think the generator should keep things simpler and users should use SwiftPM features, and when you think that the generator should put some effort into fixing something although SwiftPM features (creating a dedicated target in this case) would solve the problem. The distinction isn't clear to me.

[czechboy0]

It's a good question, it's certainly somewhat nuanced and requires making judgement calls.

In this case the generator has aimed to generate fully qualified type names in its implementation from the start. So not doing so for Error is more of an oversight, not by design, and now that an adopter has hit it, we'd accept a PR fixing the bug.

That's different to feature requests like adding an extra namespace around generated types - that's an example of something we chose not to implement, because the solution is right in SwiftPM, as you point out, as modules.