lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Tue, May 29, 2018 at 9:53 AM, Roberto Ierusalimschy <> wrote:
>      Just musings, but... I hope they get in, and I hope that `lua_keyin`
> as well as the potential hypothetical `lua_keyvalue` include versions that
> get integers and fields for number / string arguments directly (as well as
> their raw version), making for a full suite that allows maximum performance
> and mimics the current Lua C API structure:
>      [...]

We have decided that, at least for 5.4, we are not going on with
the nils-in-table proposal. Although we really like the idea, the
compatibility problems seem too big. As this message evidentiates again,
the language would need a lot of extra stuff (metamethods, API calls,
etc.), even when the option is off.

-- Roberto

: - (

That's too bad.  The behavior of holes in tables was a huge block for me when I started using Lua (and is still a pain in the ass IMO). I think allowing nil in tables removes a hole in the language (pun intended) and makes tables jmore friendly for newcomers and more practical for using as a sequence. Are we going to have to wait another 4 years for you to tease us with the possibility again?

This is very disappointing news. (To be clear, the news disappoints me, not the people or the language. No flaming necessary).