lanes/unit_tests/scripts, branch master A mirror of https://github.com/LuaLanes/lanes.git https://git.lua4.win/lanes/atom?h=master 2026-02-26T10:02:55+00:00 change cancel_test() to raise cancel_error on hard-cancels by default 2026-02-26T10:02:55+00:00 Benoit Germain benoit.germain@ubisoft.com 2026-02-26T10:02:55+00:00 urn:sha1:4f97720e4c3944ccf9b9742028dc697c2dd94c5a Improve cancel_test() documentation and unit test 2026-02-26T09:17:36+00:00 Benoit Germain benoit.germain@ubisoft.com 2026-02-26T09:17:36+00:00 urn:sha1:6b8c83b3bc44b0a1bc186f58de0fea6dfc214c4b Test full userdata keys with verbose_errors 2025-10-30T09:02:27+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-10-30T09:02:27+00:00 urn:sha1:dfb4a035c2d80a6be689e14ca495b8ba032f58c4 Stronger test for verbose_errors 2025-10-30T08:38:43+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-10-30T08:38:43+00:00 urn:sha1:9c768185696879c6642c1f26c86884eaf727fe27 verbose_errors improvement 2025-10-27T07:43:22+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-10-27T07:43:22+00:00 urn:sha1:5e5bcf37450d07f7f2812255bbd1df35d8e6ce75 * Use std::format instead of sprintf for verbose errors when decoding table keys * Add a unit test for the different table key types Lift restriction on functions and userdata as table keys 2025-09-30T13:06:21+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-09-30T13:06:21+00:00 urn:sha1:ae43a00657a6505910010bdf920c9c0f4823a9c0 As demonstrated by the unit tests, there is no problem with using a function or a userdata as a table key, as long as they are transferable Lift restriction on tables as table keys 2025-09-29T15:11:58+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-09-29T15:11:58+00:00 urn:sha1:f011dcafb0f583c89ed9971238fd83ddcbdb5438 As demonstrated by the unit tests, there is no problem with using a table as a table key Copy deep_userdata_example test script in the test framework 2025-07-31T16:35:42+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-07-31T16:35:42+00:00 urn:sha1:ab941c943aedf8f233619773c09c0fde304b8e93 * I need to keep deep_userdata_example hackishly built-in inside the unit tests executable, because using the external module cause a crash in Lua51 tests (module is unloaded before some deep objects are GCed...) * copy the test script in the proper location and invoke it as part of the tests Rework function bytecode dumping to be Lua5.5-ready 2025-07-24T14:51:49+00:00 Benoit Germain bnt.germain@gmail.com 2025-07-24T14:51:49+00:00 urn:sha1:d8acb18ce8bf6e89a042d166f61b2934e8722cf0 * prepare the luaL_Buffer in the destination state instead of the source state to prevent stack issues when everything happens in the same state Added Lua 5.5 support 2025-07-04T12:54:36+00:00 Benoit Germain benoit.germain@ubisoft.com 2025-07-04T12:54:36+00:00 urn:sha1:7bddb06461d8f80030b3b86175ec737dbb16ac3b * some unit tests fail/segfault/freeze, but that could be because Lua 5.5 is still in beta yet