Re: worst case time using hash-tables in Lua

[Francisco Olarte <folarte@...>]

Coda:

On Thu, May 14, 2020 at 8:20 PM Coda Highland <chighland@gmail.com> wrote:
> On Thu, May 14, 2020 at 12:51 PM Andrea <andrea.l.vitali@gmail.com> wrote:
*** IIR this was actually written by me ****
>>> Just be careful on taking the manuals as a normative reference, I used
>> I am not sure I understand. Why I should not take manuals as a reference?
>> (BTW it is true that code never lies, comments sometime do)
> It's not that you shouldn't take it as a reference. It's that the Lua manual only documents the intended behaviors. It doesn't document anything about implementation details, unexpected gotchas to watch out for, or how Lua acts outside of the documented behaviors.

Not arguing on these. What I meant was not that manual documents only
intended behaviours. My concrete past problem regarding this is I
always considered a local variable could not be collected until the
scope containing it ended, from manual reading, RI told me more or
less not to count on it ( IIRC, implementation does not collect, but I
saw that l8r, I didn't rely on source, I relied on manual reading ), I
noted it and acted accordingly.

> There's a reasonable argument that the manual shouldn't be expected to do anything but document the intended behaviors, so this isn't meant to be a criticism. It just isn't the ultimate answer for every question you might have about the language, and it isn't trying to be.

That was more or less my problem (MY, not the rest of the people
problem), either the manual is too complex for me or too lax in its
definition, either way, it can be solved in a resonable easy wat.

Just trying to clarify my original comment, not arguing on any of your points.

Fancisco Olarte.
_______________________________________________
lua-l mailing list -- lua-l@lists.lua.org
To unsubscribe send an email to lua-l-leave@lists.lua.org