LuaJIT 3.0 opens the floor on syntax extensions — with guardrails

LuaJIT’s maintainer has opened an umbrella GitHub issue to coordinate the syntax extensions planned for the 3.0 release, inviting structured discussion on their design and semantics. The first comment is intended to become living documentation, and two older feature-request threads have been closed and folded into this one. The maintainer also takes the chance to consolidate LuaJIT’s scattered extension docs into a single free-standing language reference, with each feature tagged by the version that introduced it.

The proposal sets explicit criteria for what gets in: an extension must improve day-to-day developer experience, already be proven in another language or Lua dialect, introduce no parsing ambiguity, preserve backward compatibility, and stay friendly to tooling like formatters and language servers. The maintainer is blunt about not wanting to import the syntactic sprawl of Perl, Ruby, C++, or Rust, while acknowledging that some choices will follow existing conventions from C, Lua, and JavaScript purely for the sake of familiarity and compatibility.

The tone of the thread is as notable as its content. Recognizing that syntax taste is subjective, the maintainer asks contributors to keep feedback constructive, accept declined proposals gracefully, and avoid bikeshedding over cosmetic symbol choices for niche operators. It’s a deliberate attempt to channel community energy toward functionality rather than aesthetics as one of the most widely used Lua implementations evolves its language surface.