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
Currently the function: decompress() speculatively attempts the following in turn:
gzdecode(...)
gzinflate(...)
self::compatible_gzinflate(...)
gzuncompress(...)
However, #3 compatible_gzinflate(...) includes within it (at Lines 834 to 838) a "fallback" call to gzinflate(...) which is identical to that attempted at #2.
Hence if #2 fails. it may be uselessly repeated within #3.
One solution may be to do BOTH the following:
MOVE the "fallback" in compatible_gzinflate(...) to the beginning of that function (i.e. make it the first inflation attempted), and
I'm new to github, but in my experience bugs/issues should be logged at an atomic level so they can be easily assessed / prioritised / managed.
In any event these aren't pull requests as I haven't actually made any code changes, I'm just highlighting them so the software author who knows his code can assess whether they have merit.
Yep, you're right about keeping things on an atomic level. The beauty of pull requests, if done properly, is that you can "cherry pick" individual changes ("commits"). It also saves the author lot of time and increase vastly the chances that he'll actually test your proposed changes :)
Currently the function: decompress() speculatively attempts the following in turn:
However, #3 compatible_gzinflate(...) includes within it (at Lines 834 to 838) a "fallback" call to gzinflate(...) which is identical to that attempted at #2.
Hence if #2 fails. it may be uselessly repeated within #3.
One solution may be to do BOTH the following:
The text was updated successfully, but these errors were encountered: