If journals are going to rehash Facebook blah word by word, syllable by syllable, then I expect free endorsements to alternatives. It's a small public service in exchange for the free content and clicks.
It's annoying. I don't use a blocker. I don't skip the ads. Yet youtube shows me some really tedious 25 minute ad (for obscure builing material; for some online god knows what; for some money scam).
I thought it must be some experiment to see how bad ads could get before people like me hit reload or start blocking, because it makes no sense otherwise.
This blocks all twitter/facebook/google/botnet widgets, other tracking elements, all ads, even those on youtube. Highly increases your privacy and browsing experience. I use these rules for so long I even forgot youtube has ads.
I use the latest uBlock Origin with the latest stable Google Chrome on Linux. I have the block lists above (https://i.imgur.com/S9pCwIc.png) enabled, and I'm still getting lots of ads on YouTube. Ads started appearing in 2018, it was fine before.
I tried putting in verified users and they were all "probably bots". By definition is that not the only type of user publicly acknowledged as "not a bot"?
Not married to the syntax, just wanted to highlight the absence of this syntax form. The syntax used was mainly meant to mirror the existing Rust pattern syntax.
As for partial matching, other languages give warnings or errors if a pattern doesn't cover all cases.
There is a whole style of programming dedicated to tail-recursion called Continuation Passing Style. It is not usually useful for programmers directly to use, because it is so complicated to read/write, but it is very useful for compilers to generate code in CPS.
If you wanted to, for example, write a new experimental functional language and reuse part of the Rust compiler to sanity check and generate the executable, then tail-recursion would be really important.
Similarly, if you create something like a parser generator and don't have tail recursion optimization, then you are going to run out of stack space before being able to parse stuff. So, there are lots of practical applications that depend on this feature too.
Ah, thanks, makes good sense. I think of "write a new experimental functional language and reuse part of the Rust compiler" as somewhat "academic", but matter of taste. But for production parsers, I think I'd try to avoid using the stack or limit the stack, anyway.
There is something disconcerting to me about titles containing the author's name. I don't care if you are famous or not, that format is for tweets, not full articles.
