Package.swift: make package name consistent with repo name

[MaxDesiatov]

Rest of SwiftPM packages provided by Apple follow a dash-case naming scheme consistent with repository name, usually with swift- prefix.

This shouldn't have any impact on SwiftPM clients, since this name argument of Package initializer is only used for display purposes and not for package resolution.

[MaxDesiatov]

@swift-ci smoke test

[neonichu]

We shouldn't follow the bad practice of the other Apple repos here. The recommended practice is naming both your package and your repository the same as your primary library product (in our case SwiftPM). Ideally, we would be able to rename the repository to a proper name, but just because that is out of the question shouldn't mean we go further down the bad path.

[tayloraswift]

The recommended practice is naming both your package and your repository the same as your primary library product (in our case SwiftPM).

i’m not sure where you are getting this recommendation from (i don’t recall any package naming guidelines existing at all), but i maintain several packages that have more than one “primary” library product. at some point, we will need to decouple package names from repository names, if only to support more than one package per repository. but i don’t think naming packages after products generalizes.

[neonichu]

but i maintain several packages that have more than one “primary” library product.

That's fine, I'm not saying that is the only way to name your package, but SwiftPM's package has its name for a reason.