monkey

Just for the record - this is package local - it's fine within the package it is defined in, but no other package will use the implementation, they will all use the standard library. Others have linked to the much more "fun" https://github.com/bouk/monkey which is an actual monkey patch, in that it changes the code that is called from anywhere in the runtime

Other prior art: https://github.com/bouk/monkey with accompanying blog post https://bou.ke/blog/monkey-patching-in-go/

https://github.com/bouk/monkey/blob/master/LICENSE.md Then why publish the blog post and put it into a package??

From the explaining blog post [0] > If you’re not interested in how it works and you just want to do monkey patching, then you can find the library here. Also > Wrapping it up in a nice library > I took the above code and put it in an easy to use library. It supports 32 bit, reversing patches, and patching instance methods. I wrote a couple of examples and put those in the README. Then in the README[1]: > Make sure you read the notes at the bottom of the README if you intend to use this library. Either the author is confused or has decided that he doesn't want to maintain an hack. Anyway license is pretty clear. There was an HN thread[2] when it was released. [0] https://bou.ke/blog/monkey-patching-in-go/ [1] https://github.com/bouk/monkey [2] https://news.ycombinator.com/item?id=9290917

Quite an unusual, but effective, way to mark something as a proof of concept that's dangerous to use: From [1]: "This is as unsafe as it sounds and I don't recommend anyone do it outside of a testing environment." [1]: https://github.com/bouk/monkey#i-thought-that-monkeypatching...

Read the license before use the library: https://github.com/bouk/monkey/blob/master/LICENSE.md Caution! This approach is very dangerous, and not thread safe.