race conditions
-
This post did not contain any content.
Noob should've used PNPM
-
I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I'm a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.
It's not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.
-
It's not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.
...are Turing Complete, so what you can do with them is exactly equal.
But they're only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.
-
It's not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.
But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?
C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.
It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.
-
This post did not contain any content.
Why is the crab not Rust. This is outrageous, it’s unfair
-
Why is the crab not Rust. This is outrageous, it’s unfair
wrote on last edited by [email protected]Rust would be some borrow checker compile error like
borrowed data escapes outside of associated functionargument requires that `'1` must outlive `'static` -
This post did not contain any content.
Why is openbsd the referee?
-
Rust would be some borrow checker compile error like
borrowed data escapes outside of associated functionargument requires that `'1` must outlive `'static`you can still segfault in rust iirc
-
I'm an 80's/90's BASIC bitch, so I'm still irrelevant!
10 PRINT "FARTS" 20 GOTO 10 -
This post did not contain any content.
Not a word of a lie, I saw a "segmentation fault" error in JavaScript.
Can't remember how we resolved it, but it did blow my mind.
-
This post did not contain any content.
I find it funny that the pufferfish blows up at its own gunshot
-
Not a word of a lie, I saw a "segmentation fault" error in JavaScript.
Can't remember how we resolved it, but it did blow my mind.
Ive also seen this, but not from js but node
-
Rust would be some borrow checker compile error like
borrowed data escapes outside of associated functionargument requires that `'1` must outlive `'static`rust errors are funny if you don't know rust
-
rust errors are funny if you don't know rust
Those also happen to be errors you'd typically run into, if you don't yet really know Rust...
-
This post did not contain any content.
No NullPointerExceptions in Kotlin.
-
rust errors are funny if you don't know rust
News at Ten: Borrowed Data Escapes Outside of Associated Function
-
As at least one nautically themed childrens' book surely has it: C is for crab.
Coming at programming sideways feels more like a Haskell or Prolog thing, though.
Apple is for ADA
Ball is for BASH
Crab is for C
Dog is for D
Elephant is for Ecsmascript
Fox is for F#
Goat is for Go
House is for Haskell
Igloo is for
...okay I got stuck there.
-
NullPointerException can be related to a race condition.
it can also not be.
-
I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I'm a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.
Or, rather, most compiled languages are just syntactic sugar on top of assembly, and that's especially true with C. (Oh, you can use curly brances and stuff for blocks? That's sure easier to read than the label mess you get with assembly.)
-
"NPM install" isn't going to be the direct result of a race condition in JavaScript. And while I'm not familiar with Python, I'd guess that an "Indentation error" wouldn't be one either. A missing library or syntax error that's only discovered by executing a particular branch is still just a missing library or syntax error, not a race condition.
Also, while Node.js is popular, it isn't an integral part of JavaScript in the way that the other errors are integral to their respective languages.
I had to come up with a title, this was it.
It's a cartoon.
