Re: What order should Lua be ported in?

[Steven Degutis <sbdegutis@...>]

>> But I assume you mean port it to use ObjC features such as classes,
>> and Foundation classes such as NSArray, NSDictionary, NSNumber, and
>> NSString.
>
> Exactly. Not as exciting a language as Swift, but you should rather be
> thinking of working in a lower-level language that remains aware of
> the particular needs of the runtime like reference counting and so
> forth - the equivalent of assembly for that platform.

Swift is actually lower-level than Objective-C, and Swift's standard
library types (Array, Dictionary) are lower-level than their
Foundation.framework counterparts. Swift is much closer to C than
Objective-C. That's a big reason why I think a port of Lua in Swift
might be useful. Especially in a few years when Swift has many
performance improvements.