SLua: pull in LL viewer updates since our fork and verify end-to-end readiness for the SLua release #430
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#430
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Keep Slipstream current with Linden Lab's SLua (Luau-based server-side scripting) and make sure we're fully ready when it leaves beta.
What we have today
7f88aedbc3add Lua as a compile target,fd82aa010cadapt to server changes,a54ac5a67fgrey out Lua on unsupported regions):luau("SLua") andlsl-luauin the script editor (panel_script_ed.xml,llpreviewscript.cpp~590);LLSyntaxLua,llscripteditor.cppinitKeywords);.luau.llcompilequeue.cpp~440,llpreviewscript.cpp~746).Tasks
Pull in LL's SLua changes since our fork. Diff LL's viewer (
secondlife/viewer, develop / release branches and the SLua project branches) for anything touching Lua/Luau. For example:LSLSyntax-style capability and its Lua equivalent, versioned keyword files);require/ module support UI;Port what's missing. Also check Alchemy and Firestorm for their SLua handling.
End-to-end verification on SLua-enabled regions (the beta grid / SLua test regions):
lsl-luau(LSL compiled to the Luau VM);.luau);Our own features with SLua:
#include/requirehelper is wanted;Watch LL's announcements and SLua status (beta → release): server-side changes that need viewer updates (new capabilities, new message fields, keyword file versions) should be tracked here or in follow-up tickets.
Done when