In-source evaluation of expressions (and in-source unit tests)

[jducoeur]

@mfcold

I would then ask, could we not simply make >>> work as a top level token, no // needed?

That’s a not-unusual symbol in some libraries – seems likely to introduce ambiguities.

[mfcold]

Fair. I still would support # over >>>, I’m just assuming that either way, making a top level token work for this should be simple enough.

[tgodzik]

@mfcold

Very cool. Though the problem with doing this within comments is that you don’t have typo detection, auto completion, type checking, syntax highlighting, etc. I assume this implementation also suffers from that?

We can fix that as well, but yeah it would require extra effort. Adding additional syntax on the other hand would require SiP, which is much more lengthy process. And the tooling would also need to catch up.

I would then ask, could we not simply make >>> work as a top level token, no // needed?

That doesn’t actually help that much as we would need to anyway support it in multiple places. The advantage of doing it in the comments is that each tool can decide or not to add this.