Lua in the kernel?

5.4 introduced (versus 5.3) consts and destructors (of a flavor), "new semantics for the integer 'for' loop" seems like it could affect kernel-oriented Lua code (and it looks like the kernel wants the new semantics of not wrapping on overflow), and string -> numbers conversions are no longer in the language, but in the stdlib. 5.3 introduced bitwise operators which seem pretty handy (5.2 added them in a library).

These are not object-oriented features, but core semantics to the language itself that seem to not be on the bottom of the list of features I'd expect in these kinds of programs.

> Thus whatever could possibly cause compatibility problems will be missing from the kernel's Lua anyway.

I mean, if it's going to be Lua 5.k, can we just call it that and make the incompatibilities with the other releases of Lua explicit?