Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Literal Containers
* '...' - Using for Atom.
* "..." - Using for Text.
* [...] - Using this for List (and maybe Map).
* {...} - Using this for Block.
* <...> - No good, as it's too hard to parse differently than < and >.
* (...) - Already overloaded for precedence and method call invocation. Tuple?
* [<...>] - Looks like a really good choice. Map?
* [!...!] - Might be too hard to parse ! inside a List then. (Unless we don't have a ! operator.)
* [@...@] - Probably too hard to parse $ sigil inside a List then.
* [#...#] - Probably too hard to parse comments then. Might use for nestable block comments.
* [$...$] - Probably too hard to parse $ sigil inside a List then.
* [%...%] - Looks like a good choice.
* [^...^] - Looks like a good choice.
* [&...&] -
* [*...*] - Looks like a really good choice.
* [|...|] - Looks like a really good choice. Set?
* [?...?] -
* [/.../] - Maybe use for regular expressions.
* %w[...] - Like Ruby variants.
* %set[...] - Like ruby variants, but with explicit names instead of hard-to-remember letters.
* [<set> ...] - Like above, but looks nicer.
* [[...]] - No good, as it's too hard to parse nested Lists then.
* [(...)] - No good, as it's too hard to parse nested precedence parens inside Lists then.
* [].set - Looks like a runtime conversion method, but is actually done at compile-time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.