Chayim Refael Friedman

Results 432 comments of Chayim Refael Friedman

Since we don't expose `setSlot()`, I don't think we should rename it. And I still think we should put it in the `meta` module: reflection is some kind of metaprogramming,...

It depends on the CSS. The https://wren.io site does: ![image](https://user-images.githubusercontent.com/24700207/116792544-f32ea180-aac9-11eb-89c4-a88c5e420416.png) ![image](https://user-images.githubusercontent.com/24700207/116792552-fe81cd00-aac9-11eb-9f14-20ffb722b7ab.png) But it's on `Bool`'s page! Please fix this.

Regarding the iterator example, we _can_ make it possible to access a variable in its own initializer, but it will be a breaking change to do that everywhere (previously this...

Another option will be to allow Go style statement before conditions: ```wren if (var a = true; a) { ... } ``` Also we may want to consider multiple variable...

There is a reason it is done this way, Bob specified it in Crafting Interpreters: http://craftinginterpreters.com/resolving-and-binding.html#resolving-variable-declarations. The disadvantage is that functions sometimes _do_ need to access themselves. This has two...

Both Java, JavaScript and Rust (and possibly others) allow to break into a label, which is more clear: ```wren outer: for (i in 1..5) { for (j in 1..5) {...

Of course not. I don't think labels are useful for anything else, but I think they're useful enough for this 😃

This works well. In example 1, you refer to **the class** `Test` and _not_ **the getter** `Test`. In example 2, there is no global variable named `TEST`, so this is...

So what do you want this to do? Break the rules? **Edit:** The only confusing part IMO is that printing a class prints its name. Maybe we should print something...

But how can we break the rules without dynamic search, which will hardly hurt Wren's performance?