4 ms·
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 rec
by philipswood 5y ago
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-in-go-is-impossible https://github.com/bouk/monkey#i-thought-that-monkeypatching...
- wereHamster 5y ago> … I don't recommend anyone do it outside of a testing environment. … which is exactly dow it is used in dapr > This is only used in the test (and thus not.compiled and distributed in our binaries). (source: https://github.com/dapr/dapr/issues/3563#issuecomment-901563861 https://github.com/dapr/dapr/issues/3563#issuecomment-901563...)
- mcguire 5y agoThere's a teeny bit of a difference between using it to explore monkey patching a go executable and using in the test suite of a released project.
- reificator 5y ago> > … I don't recommend anyone do it outside of a testing environment. > … which is exactly dow it is used in dapr Eh... There's a difference between "a testing environment" as used in that quote and "as part of an automated test" as you mean here. To me the former implies an experimental and/or ad-hoc environment, while the latter implies a stable, production environment.
- Fuzzeh 5y agoYou don't have the right to use it, even in a testing environment. The license denys you the right to use it.
- philipswood 5y agoYes, but at the same time demonstrates the code clearly so you could implement it yourself. I'd say this is code sharing aiming at zero reuse.