Re: Are the values of objects the references to them?

Things in JS are passed (to functions) by value, because direct assignment to the binding isn't visible outside the function (take no note of sloppy-mode `arguments` over there behind the curtain. ES Module live-bindings of exports add a wrinkle, as well) I've found

Re: Are the values of objects the references to them?

this… > On Aug 26, 2017, at 1:26 PM, Michael Dyck wrote: > > Another > reason might be to avoid making a distinction that the spec will never (or > rarely) use. > > When you pass a value to a function-parameter or assign a value to a > variable, you are (in spec terms, more

Are the values of objects the references to them?

Hi all, I've been struggling finding information on this, so let me open by asking the following question: Q1: If primitive types are passed by value and objects by reference when calling function, where is this characteristic of objects mentioned in the standard? I've been trying to find

Re: Re: Native Function Composition

On Sat, Aug 26, 2017 at 3:07 AM, Jordan Harband wrote: > > "incompatible" is a very strong and likely incorrect claim. `(sync1 |> sync2 |> async1).then(x => x |> sync3 |> async2).then(x => async3)` could work just fine. Or indeed, a robust proposal might allow for async