antipatterns.ko
antipatterns.ko copied to clipboard
End-user sign bit overflow during fork()
At the time of writing there are 4 forks of this repo on Github. This poses a problem: should downstream improvements to the module be classified as bugs, and changes that worsen it as fixes? Is the act of forking this project a form of resource leak?
:)
Though, more seriously, the idea is to make "interesting" mistakes (for some definition of "interesting"), all of which should have a comment next to them. If I've made a mistake that isn't commented, please let me know! The idea is to be an integration test for checking what problems static and dynamic tools can detect.