85 karma · joined January 21, 2015
The removal of scanning for changed userdata finalizer meta method in 5.2 is just a commonsense fix for bad design that made GC atomic phase run time, thats not incremental scale up with the number of GC userdata objects alive no matter if they have a finalizer or not.
[1]: https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/lj_alloc.c
[2]: https://github.com/LuaJIT/LuaJIT/blob/707c12bf00dafdfd3899b1...
https://github.blog/engineering/architecture-optimization/cr...
[1] https://web.archive.org/web/20250517130138/https://venusoft....
[1] https://github.com/yrnkrn/zapcc
[2] https://lists.llvm.org/pipermail/cfe-dev/2015-May/043155.htm...
[1] https://www.reddit.com/r/wow/comments/9huows/ama_former_wow_...
[2] https://www.reddit.com/r/classicwow/comments/9fb2bo/john_sta...
Although not sure if it has ever changed before though just by quickly scanning the change log for this app people were using to set it https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-...
1: C++ Function Multiversioning in Windows https://www.youtube.com/watch?v=LTM1was1dTU