Gavin King comments

Results 1136 comments of


                                            Gavin King

Object members switch

No, it's not possible *today*, but in principle it would be pretty simple to add.

Code compiles but causes JS Runtime error.

Note that the bug only affects expressions like `Item.make`. It does not occur for`this.Item.make`.

Code compiles but causes JS Runtime error.

I guess it's because there is no `new` anywhere, so `this` is pointing to the wrong thing.

Code compiles but causes JS Runtime error.

The problem is in `FunctionHelper.generateCallable()`, I'm just trying to coax it into generating the right code.

Code compiles but causes JS Runtime error.

I've fixed this, I believe, but still need to add a test.

replace 'smaller', 'larger', 'equal' with 'Comparison.smaller', 'Comparison.larger', 'Comparison.equal'

> Couldn't you still import them from inside the class? Yes, of course.

replace 'smaller', 'larger', 'equal' with 'Comparison.smaller', 'Comparison.larger', 'Comparison.equal'

> Also, were you planning of keeping the toplevels as deprecated until say 1.5? I guess we could do that.

replace 'smaller', 'larger', 'equal' with 'Comparison.smaller', 'Comparison.larger', 'Comparison.equal'

>> Also, were you planning of keeping the toplevels as deprecated until say 1.5? > > I guess we could do that. Except 1.4 is the release that is breaking...

replace 'smaller', 'larger', 'equal' with 'Comparison.smaller', 'Comparison.larger', 'Comparison.equal'

Yes, there is an `aliased` annotation already.

replace 'smaller', 'larger', 'equal' with 'Comparison.smaller', 'Comparison.larger', 'Comparison.equal'

> What _has_ really bugged me is the top-level function `smallest()`, which is ungrammatical for `smaller()`. Right, well that's the thing, I always wanted to call that function `smaller()`. But...