[Feedback] NIO-based HTTP Client

[johannesweiss]

@Diggory

The package namespace clash issue seems like it will only get worse and worse.

I notice that it was discussed three years ago (Revisiting package conflicts)

How about if package manifests had a macOS-style 'bundleID' in reverse DNS style? Then you could use the short package name, until there was a clash, then the compiler could prompt you to use the unambiguous bundleID instead? (I have put literally seconds of thought into this idea and have no idea how anything is implemented under the covers!)

I totally agree with you. To truly solve it, we need will need improvements very likely both in the language as well in the package manager. We started talking about this topic in the SSWG recently and I'm sure there will soon be public discussions about properly solving the problem in the language. As @tkremenek said on the SSWG call, right now "this is an inherently under-designed space" and I think there's widespread agreement that the status quo in Swift just isn't good enough.

However, we can't just wait until the problem is resolved properly and therefore, as a stop-gap, we're trying to avoid conflicts as much as possible by trying to avoid them with Github searches . I'm hoping that buys us enough time until we can solve this properly.

@Aciid

This is not a trivial problem but we do need some solution in the long term. @johannesweiss @jrose can you post a summary of the problems somewhere?

Yes, I'm working on the summary part that affects the source level, sorry that this is taking a while.

We should however separate the clashing issue in the language from the HTTP client that is proposed here. I don't think anyone expects the language level problems to be solved before we tag the first version of the HTTP client.