| 17:53 | <shu> | was OOO yesterday, looking now |
| 17:53 | <shu> | the new stuff is all contained in https://github.com/tc39/ecma262/pull/1713/commits/efc369b2322287f3b946d6fdaa7811a381bd4164, yeah? |
| 17:55 | <bakkot> | yup |
| 17:55 | <bakkot> | other than the straightforward rebase changes which probably do not require review |
| 18:11 | <shu> | dfns are case sensitive, right? |
| 18:13 | <bakkot> | uhhh mostly yes? |
| 18:13 | <bakkot> | if you define a term with a lowercase letter it will also match with the first letter uppercased |
| 18:14 | <bakkot> | like if you define example then Example also matches |
| 18:14 | <bakkot> | but they case sensitive except for that behavior, yes |
| 18:23 | <shu> | i was wondering why Range got dfn'd and State didn't, presumably because State is way too common a word |
| 18:28 | <bakkot> | it's because michael complained about introducing a new term without dfn'ing it, even though the other terms in that section are not dfn'd |
| 18:28 | <shu> | that's not a good reason |
| 18:29 | <bakkot> | https://github.com/tc39/ecma262/pull/1713#discussion_r824268425 |
| 18:29 | <shu> | though i can appreciate different philosophies around how to improve a section that is pretty divergent with the rest of the document |
| 18:29 | <shu> | one may be to fix things ad-hoc as we notice |
| 18:29 | <shu> | another one may be to minimize churn and do nothing until we can look at it holistically |
| 18:30 | <bakkot> | yeah |
| 18:30 | <bakkot> | I would have gone for consistency, personally, but also we want to refactor this section as soon as we get the two major regex PRs landed anyway so I don't really mind |
| 18:30 | <shu> | yeah |
| 18:30 | <shu> | +1 to that, the fact that it's been on our radar for a while makes me not care so much |
| 18:32 | <shu> | stamped |
| 20:02 | <Michael Ficarra> | @shu somehow you leave feedback that I can't respond to |
| 20:02 | <Michael Ficarra> | also I don't know what you mean there |
| 20:09 | <bakkot> | Michael Ficarra: this is a weird github thing; that feedback is a reply to a comment you made and will show up also in that comment theread, where you can reply to it |
| 20:21 | <Michael Ficarra> | bakkot: I don't see it |
| 20:26 | <bakkot> | Michael Ficarra: https://github.com/tc39/ecma262/pull/1713#discussion_r824995616 |
| 20:35 | <shu> | Michael Ficarra: i was asking why was math notation, e.g. < changed to "less than or equal to" in prose |
| 20:37 | <Michael Ficarra> | oh, I explained that in https://github.com/tc39/ecma262/pull/1713#discussion_r824263540 |
| 20:38 | <Michael Ficarra> | the part I was describing as not an accident there was the change from less-than to less-than-or-equal |
| 20:39 | <Michael Ficarra> | however, the change to prose also was not an accident |
| 21:22 | <shu> | and what was the reasoning for changing to prose? |