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
I am not sure what causes binaries (like simple client example binaries) to be as big as they are (multiple MB in release mode), but it might be due to monomorphization of some core functions.
Maybe things could be slightly improved using the "non-generic inner function" trick for some of these generic functions?
The text was updated successfully, but these errors were encountered:
With the updates to hyper 1 / reqwest 0.12 / axum 0.7 and some changes to the client interface, example binaries are now ~30% smaller. Not sure which change contributed how much to this improvement, but just ~2MB per application binary seems pretty good now.
I am not sure what causes binaries (like simple client example binaries) to be as big as they are (multiple MB in release mode), but it might be due to monomorphization of some core functions.
Maybe things could be slightly improved using the "non-generic inner function" trick for some of these generic functions?
The text was updated successfully, but these errors were encountered: