From 9842aa481587727d56329d138e7d8c33fb7c1ed7 Mon Sep 17 00:00:00 2001 From: Erica Marigold Date: Sat, 6 Jul 2024 22:14:06 +0530 Subject: [PATCH] Fix innacurate lua design point in luau post --- src/content/posts/luau-for-js-devs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/posts/luau-for-js-devs/index.md b/src/content/posts/luau-for-js-devs/index.md index 0e26841..4f78701 100644 --- a/src/content/posts/luau-for-js-devs/index.md +++ b/src/content/posts/luau-for-js-devs/index.md @@ -21,7 +21,7 @@ Luau has significantly diverged from Lua, with many performance improvements (in Compared to JavaScript, Luau does not face most of its well-documented pitfalls – see [wtfjs](https://github.com/denysdovhan/wtfjs). This is mainly because Luau inherits a lot of Lua’s good design decisions such as: * No two different types can be equal -* Type coercion isn’t a thing, types must be converted explicitly +* Type coercion is rare and mostly sane (it usually behaves how you would expect it to) * Arithmetic and non-arithmetic operators aren’t of the same syntax * Practically only one data type: the table, which can be used to implement virtually anything * No semicolons or indents required!