My Firefox package updates are usually slow, limiting downloads to <500kb. So, whenever the download speed used to drop, I knew Firefox released an update.
So when the XZ articles started popping up, the first thing I did was verify all sources.
There are plenty of languages with warts at least as bad as JavaScript’s. Bash, PHP, C, even relatively sane languages like Python still have huge issues like implicit variable declaration.
Nope. In Rust, a semicolon denotes a statement while a lack of semicolon is an expression so you can’t just omit them at will. This does lead to cool things though like if/else blocks being able to produce values if they end in an expression. But the expression type is checked so you’re less likely to make a mistake. You can see an example here: doc.rust-lang.org/rust-by-example/…/if_else.html
In JavaScript I never skip semicolons because I’ve seen those subtle bugs.
Like @deadbeef79000, I was bothered by the contraction. So I decided to Google it in the hopes of explaining why exactly it’s wrong, in case you’re a second-language speaker.
I honestly thought there would be a simple explanation, but it turns out that there doesn’t seem to be one. I found one Reddit thread which linked to a now-defunct blog (luckily, [it’s still available through the Wayback Machine), another that linked to an earlier Reddit thread, inside of which was yet another link to an even earlier thread. Here’s the most recent of the threads in that chain if anyone wants to read it. But below is quoted the important bit from that archived blog post:
You CAN end a sentence with a contraction if it is a Type 2 (Verb-Negative), both in speaking and writing. You are always in safe territory when you end a sentence with a negative contraction.
Examples:
No, I don’t.
I’m a student, but she isn’t.
For a Type 3 (Modal + “have”), English expert Eugene Mohr says in his article in TESOL Quarterly, “The Independence of Contractions”, that “no contraction takes place if….have occupies the final position” in a sentence. HOWEVER, Mohr limits his explanations to contractions in written language, not spoken. In informal speech, native speakers often contract a modal with “have” at the end of a sentence. So, while it looks funny written out, you will hear people end a sentence this way.
Example:
I didn’t go to church, but I should’ve.
Last, and most importantly, you CANNOT end a sentence with contraction if it is a Type 1 (Pronoun-Verb). Not in formal English, not in informal English – never! In this case, you must write out the entire verb that follows the pronoun. So take a look at the contraction at the end of your sentence. Does it contain a pronoun? If it does, then break it up into its two original words.
INCORRECT: Yes, we’re.
CORRECT: Yes, we are.
But the bottom line is yeah, the title here uses a contraction in a way that is not permitted by standard English prosody.
Yeah for sure it is. The biggest difference is that there’s a fairly simple way to explain the adjectival order: “opinion, size, age, shape, colour, origin, material, purpose”. It’s apparently very difficult to explain when you can and cannot use contractions in a concise way.
Neat FP style. Pretty verbose though. Someone should invent a terser syntax so you don’t need to write do_two_things everywhere. It’s a common operation so maybe it could even be a single character.
If you know about rust you know it’s a programmable programming language, meaning that you can make macros. There could be a macro that would do that but 1. Macros is rust code to write rust code so they have the complexity of rust squared 2. I said to myself the only macros I will allow myself to use in this challenge is println and allow
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.