[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Suggestion for 5.3: import() for creating a "slew" of locals
- From: steve donovan <steve.j.donovan@...>
- Date: Sun, 17 Nov 2013 10:33:36 +0200
On Sun, Nov 17, 2013 at 10:00 AM, Sir Pogsalot <email@example.com> wrote:
> - localize() instead of import() so it doesn't get confused as having some
> function like require()
> - I'm not saying let's get rid of all the 'local a = module.a' lines, just
> provide this for when you need to create a lot of locals
This is definitely one of those feature requests that happens every
few years! And yes, 'import' is confusing by association with Python.
But the point to understand is that this must be a purely _static_
operation at compile time. So implementing something like 'using
table.*' hits the problem of determining the contents of 'table' at
compile time. So it would have to be an explicit list of entries to
localize, and understood as syntactical sugar for all those pesky
'local insert = table.insert' statements.
The issue then is that Lua is a 'reduced carbohydrates' language that
does not provide much sugar in the product, expecting users to add
Personally, I think such a construct would be useful, but unlikely to
get much traction.