luau-lang/luau
1
0
Fork 0
mirror of https://github.com/luau-lang/luau.git synced 2025-04-07 20:30:53 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update performance.md

Browse source 
Remove outdated statement about table["field"] since we optimize it now the same way as table.field.
This commit is contained in:
Arseny Kapoulkine 2021-06-14 10:53:26 -07:00 • committed by GitHub
parent 0fdf8824f1
commit 40a175499e
Signed by: DevComp
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/_pages/performance.md
View file

@ -45,7 +45,6 @@ Table access for field lookup is optimized in Luau using a mechanism that blends
As a result, field access can be very fast in Luau, provided that:
- The source code uses `table.field` notation. The compiler doesn't optimize `table[field]` as it assumes that in this case `field` is not a string and/or can change for different accesses. Because of this you should avoid using `table["field"]` which isn't idiomatic anyway.
- The field access doesn't use metatables. The fastest way to work with tables in Luau is to store fields directly inside the table, and store methods in the metatable (see below); access to "static" fields in classic OOP designs is best done through `Class.StaticField` instead of `object.StaticField`.
- The object structure is usually uniform. While it's possible to use the same function to access tables of different shape - e.g. `function getX(obj) return obj.x end` can be used on any table that has a field `"x"` - it's best to not vary the keys used in the tables too much, as it defeats this optimization.