| 02:19 | <pokute> | Let spread them all to evaluate them: Fortunately I don't think there's any real case for having a pipeline token immediately followed by an identifier(?) so chance of writing something like |
| 02:20 | <pokute> | But we actually do have a yet unmentioned single-character that is extremely available for use: \ |
| 02:24 | <pokute> | Though \ looks weird for a topic identifier for pipelines, I don't see why it can't be used as metacharacter for (rip) records and tuples. \[0, 1, 2] |
| 03:03 | <pokute> | Finally, I'm of the opinion that the dev reality of syntax highlighting, in-editor parsing and formatters should be taken into account. Just because we can mimic PERL with existing JS to construct the most devious brain teasers for our wetware tokenizers we shouldn't expect to anyone really developing anything even close to that. I already find it more taxing to read JS that doesn't color the identifiers from operators and parentheses so having the pipeline topic styled helps already a lot. It should be a concern of course, but not a very big one. |
| 03:04 | <pokute> | For example, the following convoluted and hasty example is rather difficult to reason as is: notFound |> addOne(#) |> (#?#^1:!#) |> console.log(#) compared to the following example where the topic token is conveniently colored differently: |
| 06:12 | <jschoi> | pokute: I’m a little confused, sorry. Are you exploring these #@, #^, etc. symbols as potential pipe topics, or are you exploring them as tokens for other future syntaxes? |
| 06:15 | <pokute> | Potential pipe topics that I don't recall having been discussed, just for completionism's sake (at least that start with #). |