GH: @dirkdev98
For now, we collect the different scopes and the initialization of variables and parameters.
For now, we collect the different scopes and the initialization of variables and parameters.
With a TIL: Array#map works on many object-likes that have the `{ length }` property. Note that the callback is only called here if the element of an index exists as well. Otherwise, use `Array.from({ length })`.
With a TIL: Array#map works on many object-likes that have the `{ length }` property. Note that the callback is only called here if the element of an index exists as well. Otherwise, use `Array.from({ length })`.
Making this post revealed a bug in CompletionRecord-handling. The `break;` value is returned from the script instead of the final statement. Got that fixed now as well.
Making this post revealed a bug in CompletionRecord-handling. The `break;` value is returned from the script instead of the final statement. Got that fixed now as well.
I've started with the real basic intrinsics and finally a way to create JS objects. Combine that with member expressions and we have `[object Object]`.
I've started with the real basic intrinsics and finally a way to create JS objects. Combine that with member expressions and we have `[object Object]`.
Also an interesting thing in the spec is that `undefined` and a few others are properties on `global`. So only now can `undefined` actually be resolved.
Also an interesting thing in the spec is that `undefined` and a few others are properties on `global`. So only now can `undefined` actually be resolved.
So with all that prep work, implementing binary expressions (1 + "foo") was really straight-forward.
So with all that prep work, implementing binary expressions (1 + "foo") was really straight-forward.