[Question/Oversight] Haxe 4 still includes `haxe.zip`

[TheDrawingCoder-Gamer]

A lot of things related to haxe.zip are dependant on if it is haxe3, even though haxe4 supports it still. Even more concerning is the fact that the uncompress and compress tools don't work on anything other than neko, even though in haxe4 they simply redirect to a crossplatform api

[Simn]

IIRC that had some really silly reasons related to haxelib, because haxelib couldn't depend on a haxelib, so these functions stayed in Haxe std.

[TheDrawingCoder-Gamer]

So haxelib uses zip tools but you would like to remove them?

[Simn]

I actually thought we moved these to haxelib already, but maybe I'm wrong... anyway, a pull request that cleans this up (and doesn't break haxelib) would be appreciated!

[TheDrawingCoder-Gamer]

Neko also looks like it depends on the haxe classes as well, which means it would probably break if it was removed entirely

[tobil4sk]

I was looking at this recently and also got confused, but the direction is actually opposite. haxe3 means haxe 3 or above, so on haxe 4 or 5 it also uses the std version, not the format version. The haxe3 condition is actually for supporting haxe 2 (so it can fall back to the original format.zip). Originally this class was in format, and it was moved to haxe std:
8524fd2#diff-40c0e2b78bf3000726d8eec81030cfd1e4d5801abb7293a5c88fdb5a97bc3e08