|
|
|
|
|
by HaroldCindy
721 days ago
|
|
>> the VM assumes that the bytecode was generated by the Luau compiler (which never produces invalid/unsafe bytecode) Yep, to that end they also have a basic bytecode verifier (only used in debug mode / when asserts are enabled) that validates the compiler only outputs valid bytecode, and I believe they continuously fuzz the compiler to make sure those asserts can't be triggered. See https://github.com/luau-lang/luau/blob/0d2688844ab285af1ef52... It's fairly robust (and Luau bytecode isn't _that_ complex,) but they made the right decision disallowing direct bytecode execution. |
|