<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua, branch v5.4</title>
<subtitle>A mirror of https://github.com/lua/lua
</subtitle>
<id>https://git.lua4.win/lua/atom?h=v5.4</id>
<link rel='self' href='https://git.lua4.win/lua/atom?h=v5.4'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/'/>
<updated>2025-08-27T17:58:02+00:00</updated>
<entry>
<title>Bug: Constructors with nils can overflow counters</title>
<updated>2025-08-27T17:58:02+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-08-27T17:58:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=934fdd481ced3a9d4a7aaace4479ce889ab23582'/>
<id>urn:sha1:934fdd481ced3a9d4a7aaace4479ce889ab23582</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bug: error with option '--' without a script</title>
<updated>2025-08-27T17:55:35+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-08-27T17:55:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=9ac9d23f4164fc7e1eeea8a3e8d4e453dade51ab'/>
<id>urn:sha1:9ac9d23f4164fc7e1eeea8a3e8d4e453dade51ab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bug: new metatable in weak table can fool the GC</title>
<updated>2025-06-16T19:33:02+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-06-16T19:33:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=1b0f943da7dfb25987456a77259edbeea0b94edc'/>
<id>urn:sha1:1b0f943da7dfb25987456a77259edbeea0b94edc</id>
<content type='text'>
All-weak tables are not being revisited after being visited during
propagation; if it gets a new metatable after that, the new metatable
may not be marked.
</content>
</entry>
<entry>
<title>New release number, updated copyright year</title>
<updated>2025-05-21T16:52:56+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-05-21T16:52:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=6e22fedb74cf0c9b6656e9fce8b7331db847c605'/>
<id>urn:sha1:6e22fedb74cf0c9b6656e9fce8b7331db847c605</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bug: check for constructor overflow in [exp] fields</title>
<updated>2025-05-20T20:55:08+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-05-20T20:55:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=267ef461d0b13aa28d667f12d1a61452c9db529c'/>
<id>urn:sha1:267ef461d0b13aa28d667f12d1a61452c9db529c</id>
<content type='text'>
The check for constructor overflow was considering only fields with
explicit names, ignoring fields with syntax '[exp]=exp'.
</content>
</entry>
<entry>
<title>Bug: Bad error message with fields of string _ENV</title>
<updated>2025-05-15T18:14:56+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-05-15T18:14:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d1ee2a4deb06a335b9ff99530917b828a7ebe3e5'/>
<id>urn:sha1:d1ee2a4deb06a335b9ff99530917b828a7ebe3e5</id>
<content type='text'>
Errors with fields of the string _ENV (e.g., ("_ENV").u + 1) report
the error as comming from a global.
</content>
</entry>
<entry>
<title>Bug: message handler can be overwritten</title>
<updated>2025-03-17T19:14:17+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-03-17T19:14:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=3fe7be956f23385aa1950dc31e2f25127ccfc0ea'/>
<id>urn:sha1:3fe7be956f23385aa1950dc31e2f25127ccfc0ea</id>
<content type='text'>
A __close metamethod can overwrite a message handler in the stack
when closing a thread or a state.
</content>
</entry>
<entry>
<title>Bug: Use after free in 'luaV_finishset'</title>
<updated>2025-03-13T18:42:39+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-03-13T18:42:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=983bc433e6a60cbc4fe3a16f1d4713bacb8e3509'/>
<id>urn:sha1:983bc433e6a60cbc4fe3a16f1d4713bacb8e3509</id>
<content type='text'>
If a metatable is a weak table, its __newindex field could be collected
by an emergency collection while being used in 'luaV_finishset'. (This
bug has similarities with bug 5.3.2-1, fixed in commit a272fa66.)
</content>
</entry>
<entry>
<title>Bug: 'luaD_seterrorobj' should not raise errors</title>
<updated>2025-03-12T19:01:03+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-03-12T19:01:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=25da574fcbb68bf507431a6091ab73ac434c9428'/>
<id>urn:sha1:25da574fcbb68bf507431a6091ab73ac434c9428</id>
<content type='text'>
This function can be called unprotected, so it should not raise any
kind of errors. (It could raise a memory-allocation error when creating
a message).
</content>
</entry>
<entry>
<title>Bug: Missing error status in panic function</title>
<updated>2025-01-16T19:25:11+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-01-16T19:25:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=f5e55be2a0ce64066c1b0554675633b92c91fafb'/>
<id>urn:sha1:f5e55be2a0ce64066c1b0554675633b92c91fafb</id>
<content type='text'>
'luaD_throw' may call 'luaE_resetthread', which returns an error code
but clears 'L-&gt;status'; so, 'luaD_throw' should set that status again.
</content>
</entry>
</feed>
