From baa081b533e772ee05500fb1a2e9835c759d813e Mon Sep 17 00:00:00 2001 From: T 'Filtered' C Date: Wed, 12 Jan 2022 19:05:29 +0000 Subject: [PATCH] Update compatibility.md Considering how coroutine.close was added recently, it would make sense to rework this document to split lua_resetthread and coroutine.close because of this, to mark one as ticked and the other as not currently available. --- docs/_pages/compatibility.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/_pages/compatibility.md b/docs/_pages/compatibility.md index 70ca77cc..7a176764 100644 --- a/docs/_pages/compatibility.md +++ b/docs/_pages/compatibility.md @@ -107,7 +107,8 @@ Floor division is less harmful, but it's used rarely enough that `math.floor(a/b | const variables | ❌ | while there's some demand for const variables, we'd never adopt this syntax | | new implementation for math.random | ✔️ | our RNG is based on PCG, unlike Lua 5.4 which uses Xoroshiro | | optional `init` argument to `string.gmatch` | 🤷‍♀️ | no strong use cases | -| new functions `lua_resetthread` and `coroutine.close` | 🤷‍ | not useful without to-be-closed variables | +| new function `lua_resetthread`| 🤷‍ | not useful without to-be-closed variables | +| new function `coroutine.close`| ✔️ || | coercions string-to-number moved to the string library | 😞 | we love this, but it breaks compatibility | | new format `%p` in `string.format` | 🤷‍♀️ | no strong use cases | | `utf8` library accepts codepoints up to 2^31 | 🤷‍♀️ | no strong use cases |