question about gotos in luau

[rugged elbow]

official luau page says that goto complicates the compiler and makes control flow unstructured, but how? doesn't luau use goto/jump instructions internally?

[buoyant heron]

** You are now Level 1! **

[gaunt steeple]

it creates a lot of problems when you try to write your gotos manually, since gotos require more gotos. just let the compiler do it's thing, you don't need to use goto.

scope becomes ambiguous when you try to use goto

;compile lua ```lua
function a(x)
x=x+1
::thing::
x=x+1
print(x)
return x
end
function b(y)
local x=y
goto thing
return y
end

local output=b(4) -- what should output be, 4, 5, or 6?``` if i wrote that right

[digital token]

Program Output

/opt/wandbox/lua-5.4.7/bin/lua: prog.lua:14: no visible label 'thing' for <goto> at line 10

.pyrofire | lua | lua-5.4.7 | wandbox.org

[gaunt steeple]

it usually doesn't pan out well in practice and makes your code unnecessarily more confusing. write closures better and you won't ever need goto.

it's the compilers job to fill in the goto's for you