| 16:46 | <nicolo-ribaudo> | Could finally start passing a parameter to its callback? |
| 16:52 | <snek> | but then we would need Promise.allFinallyed |
| 17:03 | <bakkot> | nicolo-ribaudo: probably; adding new parameters is rarely breaking. but what parameter are you thinking of? |
| 17:27 | <Ashley Claymore> | finally could be given the same as settled? |
| 17:39 | <bakkot> | Ashley Claymore: I can't parse your comment at all |
| 17:39 | <bakkot> | can you say that again but with more words |
| 17:45 | <Rob Palmer> | If your company has the space (or the funds to rent a venue) and desire to host a TC39 plenary meeting in 2024, please reach out to the Chairs 🙏
|
| 18:02 | <Ashley Claymore> | How about more code?.finally(({status, value, reason}) => ... ) |
| 18:06 | <bakkot> | ah, yeah |
| 18:06 | <bakkot> | that's a thing we could do but wouldn't actually do the thing I want |
| 18:07 | <bakkot> | I guess you could do .finally(x => x) to get the thing I want |
| 18:07 | <bakkot> | but that would be kind of odd |
| 18:13 | <Ashley Claymore> | I guess you could do |
| 18:13 | <Ashley Claymore> | and rejecting too I guess |
| 18:13 | <bakkot> | yeah, true |
| 18:13 | <Ashley Claymore> | So that would be a difference between .settled and .finally, the first would allow a change in the resulting promise's resolved value |
| 18:14 | <bakkot> | that comment I do not understand |
| 18:14 | <bakkot> | settled as I've proposed it doesn't take a callback |
| 18:15 | <bakkot> | so there's not anything to be making changes |
| 18:15 | <Ashley Claymore> | Ah right. I keep just merging a following .then thinking of it as a callback to settled |
| 18:15 | <Ashley Claymore> | It's almost like it lates on a Friday and I'm off on holiday next week. Brain shutdown |
| 23:54 | <ljharb> | we can't do that for .finally() because it wouldn't match a finally block, in which you don't have that info |