jondot / goweight

A tool to analyze and troubleshoot a Go binary size.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Does this have to leave behind a binary?

BryanNoller opened this issue · comments

Does this have to leave behind a binary when used on a “package main” after execution has finished?

Not at all, it can clean it up. If you want to add this I’ll accept PR. Otherwise I’ll add this as a task and implement as time allows
Thanks for the observation!

I honestly haven't looked at the code yet, but it would be nice if possible to not write binary to disk in the first place, or write to a temporary file with a randomized unique name. Currently if you have a file in existence already, possibly unrelated to a compiled binary, it gets replaced.

Done! please take latest release :)