Maybe having a way to enforce that on the compiler. So you can force the compiler to tell you it couldn't eliminate heap allocations.
Maybe having a way to enforce that on the compiler. So you can force the compiler to tell you it couldn't eliminate heap allocations.
Basically you can run the Go compiler with the escape analysis output flags, and have a script process its output, breaking the build if there are too many of them, or whatever condition you feel like.
Don't folks brag about UNIX philosophy all the time around here?
Here is a good scenario for some pipelining with Make, awk, sed, perl and co.
I'm reminded of tail call recursion in C.
Compiler noid: We added tail call recursion. Is super you should use it!
Me: Can I guarantee it will actually do tail call recursion?
Compiler Noid: If course not!
Me: Nope.