I’m questioning if its doable to construct Go from supply with protection instrumentation such that everytime we execute go run or go construct we will examine the protection on the go compiler supply code.
Hello @PanickyPeguin,
Would utilizing a Makefile work?
(Edited so as to add: I imply, as an alternative of recompiling the Go toolchain. You may arrange make targets with the -cover flag to construct the code with protection enabled.)
Edit 2: Or do you need to measure protection of the compiler itself?
This sounds suspiciously like DevOps to me. Check out this:
This might push the onus of worrying about protection to your pull requests and such. Apart from that, assuming you’re utilizing bash, possibly you possibly can alias the command in your ~/.bashrc? For instance, I aliased my npm command like so:
alias npm="winpty npm.cmd"
So it makes use of winpty (I’ve a sophisticated setup whereby I’m utilizing git bash on Home windows and winpty makes colours work with npm).
Hello @christophberger I imply measuring the protection of the compiler itself
