Hello! I'm nfi-hashicorp from https://github.com/actions/setup-go/issues/395 https://github.com/actions/setup-go/issues/395 :) My 2c given that that issue has

Hello! I'm nfi-hashicorp from https://github.com/actions/setup-go/issues/395 https://github.com/actions/setup-go/issues/395 :) My 2c given that that issue has sat in TODO for several years with no movement is that the maintainers probably aren't going to be pursuing too many big swings like that. End of the day, implementing an efficient GOCACHE with github's cache primitives is untenable for the general case IMO. It works by shipping around big tarballs, and when your cache actually needs fine grained access to thousands of usually tiny files, only a few of which change, you're likely gonna spend more time on transfer and unpacking than you gain with cache hits. The other thing is, as mentioned elsewhere, it's really hard to measure cache perf at a granular enough level, and aggregate that across jobs, so I'm willing to bet most people don't (outside of this very good post!) and are going off of vibes or napkin math and don't realize they're wasting time caching garbage.