03:12 | <Domenic> | rbuckton: I'm trying to figure out what's included and what's not included in proposal-explicit-resource-management with regards to async resources. There's still @@disposeAsync , but... no syntactic support for calling it?? Is that right? |
03:14 | <Domenic> | I very much appreciate the analysis of web platform & Node.js objects BTW |
09:39 | <nicolo-ribaudo> | Does ecmarkup support something like break; ?
Or in order to do this:
1. Let _found_ be *null*.
2. For each Record _x_ of _y_, do
1. If ..., then
1. Set _found_ to _x_.
2. Break.
Do I have to manually iterate over y?
1. Let _found_ be *null*.
2. Let _len_ be the length of _y_.
3. Let _i_ be 0.
4. Let _stop_ be *false*.
2. While _i_ < _len_ and _stop_ is *false*, do
1. If ..., then
1. Set _found_ to _x_.
2. Set _stop_ to *true*.
2. Set _i_ to _i_ + 1.
|
10:00 | <Jack Works> | 1. Let _wrapperList_ be a List of the same length with _y_ whose each element _O_ is ! OrdinaryObjectCreate(*null*, « [[WrappedSpecValue]] ») and _O_.[[WrappedSpecValue]] has been set to the coresponding value in _y_ in _y_'s order.
2. Let _finder_ be a new Abstract Closure with parameters (_currentValue_) that captures ... and performs the following steps when called:
1. If ..., then
1. Return *true*.
2. Return *false*.
3. Let _finderF_ be CreateBuiltinFunction(_finder_, 1, "", « »).
4. Let _foundResult_ be ! Call(%Array.prototype.find%, ! CreateArrayFromList(_wrapperList_), « _finderF_ »).
5. If _foundResult_ is *undefined*, then
1. ...
6. Let _matched_ be _foundResult_.[[WrappedSpecValue]].
Just a joke LOL
|
12:18 | <sachag> | hi all! just a quick message to let you know that I've started work on the 2022 edition of the State of JS survey |
12:19 | <sachag> | there's an open GitHub thread to collect feedback here: https://github.com/Devographics/surveys/issues/47 |
14:27 | <littledan> | Thanks for reaching out sachag! |
15:27 | <bakkot> | nicolo-ribaudo: it does not support break . easiest thing in your case is probably
1. Let _found_ be *null*.
1. For each Record _x_ of _y_, do
1. If _found_ is *null* and ..., then
1. Set _found_ to _x_.
or similar
|
15:28 | <bakkot> | though you can early exit AOs with Return so an alternative is to factor out an AO, if it makes sense to do so in your case |
15:40 | <annevk> | no KitKats for you |
21:58 | <rbuckton> | rbuckton: I'm trying to figure out what's included and what's not included in proposal-explicit-resource-management with regards to async resources. There's still @@disposeAsync , but... no syntactic support for calling it?? Is that right? For now, yes. Syntactic support is still planned, but it was suggested that we reduce the scope of the proposal in an effort to reach Stage 3. Syntactic async dispose is still under debate due to concerns about the implicit await that is introduced. See https://github.com/tc39/proposal-explicit-resource-management/issues/101 for the current status of that issue. |