You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussion on which solution is a better solution,
vendored copy of zlib SwiftPM package
system copy of zlib.
as @Lukasa proposed using a separate SwiftPM package that is appropriately versioned and then add an appropriate dependency on it.
rather than integrating vendored copy of zlib into the swift-nio directly (-1 form @Lukasa)
if swift-nio 2.0 goes with the vendored copy of zlib SwiftPM package, then the swift-nio adopters can use same SwiftPM package.
The text was updated successfully, but these errors were encountered:
To be clear, I am also opposed to depending on a SwiftPM zlib package. I think the most interesting alternative would be a well-maintained Swift implementation of gzip and deflate.
Until that time I think I’d rather use the system zlib.
Discussion on which solution is a better solution,
as @Lukasa proposed using a separate SwiftPM package that is appropriately versioned and then add an appropriate dependency on it.
rather than integrating vendored copy of zlib into the swift-nio directly (-1 form @Lukasa)
if swift-nio 2.0 goes with the vendored copy of zlib SwiftPM package, then the swift-nio adopters can use same SwiftPM package.
The text was updated successfully, but these errors were encountered: