Re: Wishful request for next version: '// 1' should produce integer

I like the big int operator idea. It’ll be far better to lose the comment introducer in some case. Just use the multi line comment —[

In terms of future interfacing to hardware, it is easy to imagine computing boxes doing fluid changes to real time video with an array of AIPEs like uniquify have just announced, but there will be more according to this article.

https://aitopics.org/doc/news:FEC52C91

So GPUs will no longer be the only alien hardware architecture that takes us beyond existing boundaries.

AIPE computers will be here before Quantum computers because of the cost and quantity of ready made high performance neural network hardware.

So perhaps because Lua is established as a scripting language for entertainment it could take up the big int package idea and make the future of 3D video games their domain.

Better to keep a simple core and have extensions in the C/C++ runtime of game engines like Gideros do than the chimera of Luau developed by Roblox.

P.s.

I’m glad people do think about their responses for as long as possible but no longer.

I usually think about it long enough to realise the order of my thinking leaves the most important at the bottom of my first response.

On 8 Jan 2022, at 21:45, Egor Skriptunoff <egor.skriptunoff@gmail.com> wrote:

On Sat, Jan 8, 2022 at 9:22 PM Flyer31 Test wrote:
PS: Why do you think that Lua has lost its "simple coding style" since
5.3?

I'm not talking about "coding style".
Let's define "complexity of a language" as the amount of information you have to load into your brains for successful programming.
Lua 5.2 was more simple (and more attractive to me) because of the single numeric type.
In Lua 5.3+ every arithmetic _expression_ might be dangerous because of occasional integer wraparound.
For example, you are writing an _expression_ for floating point values, but some of the variables might sometimes contain integers, they may come from user input, from function's arguments, from the length operator, from str:byte(), from next(t), from simple constants you have forgotten to convert into floats (such as x=1). In other words, Lua always tries to poison your arithmetic with integers, and you have to fight back these attacks :-)
You have to make sure that either the result of a multiplication is always within the integers range or at least one of the operands is float.
That's a new complexity and new source of errors Lua 5.2 did not have.

Was Lua 5.3 designed with the assumption that integer wraparound is a useful feature? :-)