| 14:22 | <DerekNonGeneric> | proposal-error-stacks is the weirdest proposal ever... i don't understand why it is even still there... it is trying to standardize SystemJS and there is misinformation on the explainer text https://github.com/tc39/proposal-error-stacks |
| 14:26 | <DerekNonGeneric> | like.. if there is no reference implementation, it should probably not say that there is (right?) |
| 15:19 | <DerekNonGeneric> | i know this org is only like ~5yrs old, so curating all these oldies and moving them elsewhere probably is not something that has come up (or perhaps it has, but something should be done) |
| 16:43 | <DerekNonGeneric> | bakkot: is there a process for removing unviable proposals? |
| 16:44 | <DerekNonGeneric> | ljharb: see the above, maybe you can help demystify |
| 17:11 | <DerekNonGeneric> | not sure how to interpret the silence, but if someone is able to make sense of this, please do get back to me. Jordan mentioned that the proposal needs to be split up; he also mentioned that it needs accessors (getters) for the stack property to function properly.. are we going to collaborate on this? how do we move this forwards? |
| 17:19 | <jmdyck> | re silence: Well, it is Saturday. Moreover, in the USA, it's a long weekend. |
| 18:48 | <bakkot> | DerekNonGeneric: proposals are removed only if withdrawn by their champion, which this proposal has not been. |
| 21:15 | <DerekNonGeneric> | good to know, thanks |