I used Svelte, made a cursed regex to split the code into words or (single) characters, assigned them a random color (with hsl(${Math.random()*360}, 100%, 50%)
), and put them back together in a pre
HTML block. Its like 20 lines of code lol
Nowhere, but if you really wanted it I could put up the svg somewhere.
Note that it incorporates the Rust logo, and trademark guidelines are that stuff like shirts with it shouldn't be sold without Mozilla's okay. Copyright-wise, the logo is CC-BY (author is Mozilla), and the crab is CC Zero.
> The claim of OP's article was that if you use square brackets for types you couldn't possibly do array notation, yet your example doesn't have any array notation.
a) The main point is that you can't parse generics using <>
without some kind of workaround – I mentioned a few in the article.
b) Trying to use []
both as generics and array access has similar issues (requiring some kind of workaround), which I didn't spell out because that wasn't the main point of the article.
> You have to look past the :: token
There is no ::
token. Adding such a token to fix parsing is a workaround that I explicitly listed in the article.
Here is another workaround, specifically about <code>[]</code> for both generics and arrays.
Those are not mentioned on the frontpage or even under https://nim-lang.org/features.html which literally lists
Indentation significant syntax Multiple constructs inspired by Python Multi-line lambdas Oberon-inspired visibility markers Pascal-inspired type sections for leaner definitions
I mean, seriously?
Generics are pretty cool, and small GC pauses are too, but what's the parallelism story here? Go has large GC pauses due to parallelism, single-threaded GC is much easier.
Exceptions though... ugh, I'll pass. Also, how do you even compile those to C without breaking ABI and introducing performance penalty?
I use an android reddit client called Boost. Appearance is very customizable, so yeah. If you want the exported app settings that I use (which includes the theme) hit me up