tbh I think it's a lot less of an issue. It's creating a new var named `true` (or `false`) - that only exists in the scope it's declared in, not globally. I t

tbh I think it's a lot less of an issue. It's creating a new var named `true` (or `false`) - that only exists in the scope it's declared in, not globally. I think it's crazy that this isn't a compile-time error, but it's not even close to "you can change the global value of builtin values".