As far as I can tell it's mostly legacy removal and adoption of (now) standardized types, such as "z_size_t" being replaced by "size_t" There is a document here that tries to describe the different considerations: https://github.com/zlib-ng/zlib-ng/blob/develop/PORTING.md "The zlib-ng native has implemented some modernization and simplifications in its API, intended to make life easier for application developers." "In certain places zlib-ng native uses more appropriate data types, removing the need for some workarounds in the API compared to zlib." In another discussion the maintainer said that compat mode still includes all of the performance improvements. There is one compatibility hiccup mentioned on the porting document which also affects compat mode, which is that if you provide your own buffer, zlib-ng needs a larger buffer than zlib regardless of which way it is compiled. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
