| 00:49 | <Sirisian> | Random question. Whatever happened to making getters and setters async compatible? |
| 00:57 | <bradleymeck> | Sirisian: lack of real need, just return a Promise? |
| 00:58 | <bradleymeck> | adding them gets a bit confusing, even doing class init async is pretty wonky but still being looked at |
| 00:59 | <bradleymeck> | also, always returning a new Promise is probably undesirable usually, and async functions always make a new promise |
| 01:04 | <Sirisian> | I had a friend writing an API wrapper. He kind of wanted to write await foo.value = 10; but instead just made the operation synchronous which locked up his main thread. (He was fine with this). I had an old project that did something similar with network calls but did .set('value', 10) type stuff. |
| 01:25 | <Bakkot> | using async `setValue` methods seems better than trying to have async setters |