| 16:25 | <TabAtkins> | Probably not, it would run into the same ambiguities that % or ^ as the topic have. |
| 16:29 | <jschoi> | Topic % and topic ^ don’t really have ambiguity...They just require tokenizer contextuality like /. I know Shu argued against topic % and topic ^ for this reason, but I wonder just how bad of a problem it would actually be in implementation. |
| 18:59 | <TabAtkins> | That "contextuality" is the ambiguity I meant - without carrying parser context, it's ambiguous. |
| 19:00 | <TabAtkins> | And it's a pretty bad problem - note the objections Waldemar had in the types-as-comments about parsing issues, of which / is one of the problems. |
| 19:07 | <shu> | "how bad of a problem it is" is that it's a pretty bad problem and we shouldn't willingly add it unless it's like, really the least of all evils |
| 19:14 | <jschoi> | I understand; it’s good to hear that again, thank you. |