commit | 59e565d9555c07e82808d8c1db8f4f4d159b5e5c | [log] [tgz] |
---|---|---|
author | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Tue Dec 29 10:23:02 2020 -0300 |
committer | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Tue Dec 29 10:23:02 2020 -0300 |
tree | 7dced733d2e01a6060d656afad903539ac2fedc9 | |
parent | 6188f3a654c0380db08eb40a5465ce8e71c784f5 [diff] |
No need to recheck close method before calling it A to-be-closed variable is constant and it must have a close metamethod when it is created. A program has to go out of its way (e.g., by changing the variable's metamethod) to invalidate that check. So, it is not worth to test that again. If the program tampers with the metamethod, Lua will raise a regular error when attempting to call it.
This is the repository of Lua development code, as seen by the Lua team. It contains the full history of all commits but is mirrored irregularly. For complete information about Lua, visit Lua.org.
Please do not send pull requests. To report issues, post a message to the Lua mailing list.
Download official Lua releases from Lua.org.