lua/lcorolib.c, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92023-05-02T19:41:43+00:00"Emergency" new version 5.4.62023-05-02T19:41:43+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-05-02T19:41:43+00:00urn:sha1:6443185167c77adcc8552a3fee7edab7895db1a9
'lua_resetthread' is back to its original signature, to avoid
incompatibilities in the ABI between releases of the same version.
New function 'lua_closethread' added with the "correct" signature.
Bug: stack overflow with nesting of coroutine.close2022-10-25T19:44:06+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-10-25T19:44:06+00:00urn:sha1:1e64c1391f9a14115b5cc82066dbf545ae73ee27Bug: Wrong status in coroutine during reset2021-11-08T14:55:25+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-11-08T14:55:25+00:00urn:sha1:bfbff3703edae789fa5efa9bf174f8e7cff4ded8
When closing variables during 'coroutine.close' or 'lua_resetthread',
the status of a coroutine must be set to LUA_OK; a coroutine should
not run with any other status. (See assertion in 'lua_callk'.)
After the reset, the status should be kept as normal, as any error
was already reported.
Broadening the use of branch hints2021-02-24T14:14:44+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-24T14:14:44+00:00urn:sha1:59c88f846d1dcd901a4420651aedf27816618923
More uses of macros 'likely'/'unlikely' (renamed to
'l_likely'/'l_unlikely'), both in range (extended to the
libraries) and in scope (extended to hooks, stack growth).
Report last error in closing methods2020-12-22T13:54:25+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-22T13:54:25+00:00urn:sha1:0ceada8da92135717d31a3954b5b89a954f9e71a
When there are multiple errors around closing methods, report the
last error instead of the original.
Keep memory errors as memory errors2020-07-06T15:09:44+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-06T15:09:44+00:00urn:sha1:b57574d6fb9071b2f8f261b32c9378ed72db7023
Allow memory errors to be raised through the API (throwing the
error with the memory error message); error in external allocations
raises a memory error; memory errors in coroutines are re-raised
as memory errors.
Fixed a warning and other minor issues2019-10-04T19:17:04+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-10-04T19:17:04+00:00urn:sha1:7bd1e53753de7176eb0b23f2bf19ad2235dec826
Fixed some minor issues from the feedback for 5.4-beta rc1.
Multiple errors in '__toclose' report the first one2019-06-05T16:16:25+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-06-05T16:16:25+00:00urn:sha1:b4d5dff8ec4f1c8a44db66d368e95d359b04aea7
When there are multiple errors when closing objects, the error
reported by the protected call is the first one, for two reasons:
First, other errors may be caused by this one;
second, the first error is handled in the original execution context,
and therefore has the full traceback.
'coroutine.kill' renamed 'coroutine.close'2019-06-03T16:11:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-06-03T16:11:20+00:00urn:sha1:514d94274853e6f0dfd6bb2ffa2e1fc64db926ddTest for dead coroutine moved to 'lua_resume'2019-05-09T14:32:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-05-09T14:32:20+00:00urn:sha1:3f253f116e8e292977a1bded964544fb35b3d1e3
The test for dead coroutines done in the 'coro' library was moved
to 'lua_resume', in the kernel, which already does other similar
tests.