lua/lcorolib.c, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12025-12-01T13:25:44+00:00In luaB_close, running coroutines do not go to default2025-12-01T13:25:44+00:00Roberto Iroberto@inf.puc-rio.br2025-12-01T13:25:44+00:00urn:sha1:985ef32248f17ae4ca2d4e83e5e39e15393bb2f6
This should had been corrected in commit fd897027f1.
The main thread cannot be closed2025-06-13T17:08:38+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-13T17:08:38+00:00urn:sha1:e657a48ea5698bbd9982d878eb65e6615ec94f7e
No thread started with pcall (instead of resume) can be closed,
because coroutine.close would not respect the expected number of
results from the protected call.
A coroutine can close itself2025-06-12T14:15:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-12T14:15:09+00:00urn:sha1:fd897027f19288ce2cb0249cb8c1818e2f3f1c4c
A call to close itself will close all its to-be-closed variables and
return to the resume that (re)started the coroutine.
llimits.h being used by all Lua code2024-06-20T17:46:06+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-06-20T17:46:06+00:00urn:sha1:a08d82eb132bfd9db5b91e0d5ebcb81d7b26dcd0
The definitions in llimits.h are useful not only for the core. That
header only defines types and '#define's, so libs and core still do
not share any real code/data.
"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.