Announcing the Networking Workgroup

Announcements
,
3

I'd also like to introduce swift-endpoint as a contender, like I've done before here in the swift forums:

  • swift-endpoint contains IPv4, IPv6, AnyIPAddress, CIDR, DomainName (w/ IDN) implementations.
  • In most cases it performs better or much-better than using the C-lib APIs, at least when called from Swift.
  • Provides what I think is a good API surface, alongside providing performant ways to convert the types to each-other (and String) where needed.
  • Has an exhaustive amount of tests. Has a good amount of benchmarks.
  • Has very low Apple platform requirements of macOS-10.15-and-friends which required a decent amount of work. I hope this is not even needed and we can just jump straight to macOS 26, but we'll have to see how realistic that is and if it doesn't block adoption of existing SwiftPM packages which follow SemVer 2.0, or such.

Knowing @camunro, I'd think either swift-cidr or swift-endpoint or a combination of both should be able to satisfy that one goal of the Networking work-group, which is a nice head-start for the Networking work-group to have, even before its inception :sweat_smile:.

6 Likes