Hi Bergi:
>You're not the only one who is unsatisfied with the current proposal :-) Also
>have a look at
Great! I’m yet to read them but I definitely will soon to discuss more.
>Promises are result values that can be passed to multiple consumers, and not
>every consumer should be allowed to
arately to gain attention and discuss.
From: Marky Mark<mailto:m...@heyimmark.com>
Sent: Wednesday, October 19, 2016 11:20 AM
To: Kagami Rosylight<mailto:sascha...@outlook.com>;
es-discuss@mozilla.org<mailto:es-discuss@mozilla.org>
Subject: Re: Alternative way to achieve cancelabl
I want to find a way to replace cancellation token in the current [stage 1
cancelable promise
proposal](https://github.com/tc39/proposal-cancelable-promises) with an
alternative way which does not require passing an additional parameter.
Here is a short representation of [my current
>From a technical point of view, using 
and it interestingly changes
>Why is this needed? Why are people trying to get the property of an object
>which is null?
I will appreciate null propagation when a function receives an “option bag”
```js
function someFunction(options) {
if(options?.foo) {
doSomething();
};
}
someFunction();
someFunction({ foo: true
>IIRC the proposed syntax for computed properties was x?.[y],
Yes you’re right, sorry :/
IMO it still seems the syntax problem is the main reason why this proposal has
stalled. If not, what is the problem here? I’m curious why this proposal is not
even listed in stage 0 proposal list.
>The token ?. works fine
I think more than half of this thread is about syntactic ambiguity, regardless
of whether the ambiguity is real or not. For example, from [an earlier post of
this
thread](https://esdiscuss.org/topic/existential-operator-null-propagation-operator#content-44):
>But
Or `!.`, which unfortunately is now being used by TypeScript?
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
You’re right, my `partial` function does not support multiple inheritance and
the input class should not have its own prototype chain. I think partial class
and multiple inheritance are two different issues, however, as the former can
work without the latter and vice versa.
Is the only problem here is the parser problem with `obj.prop?.2:.1`? Then how
about `??. ` instead of `?.`?
>Once upon a time, there was a fascinating proposal on this subject:
Why are you posting twice? :/
___
es-discuss mailing list
I’m not sure it’s okay to reply on this very old thread, but if I’m
understanding correctly the desugared code can be fairly short with new
Object.getOwnPropertyDescriptors:
```js
function partial(base, extension) {
extension.prototype.__proto__ = base.prototype.__proto__; // to enable
11 matches
Mail list logo
