HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-21日前Why make it complicated?lemmy.mlimagemessage-square96fedilinkarrow-up1308arrow-down126file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up1282arrow-down1imageWhy make it complicated?lemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-21日前message-square96fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squarecalcopiritus@lemmy.worldlinkfedilinkarrow-up13·22時間前It’s also valid rust syntax. But if it were rust, this meme would not make sense, since you would just type let a and type inference would do its thing. Which is much more ergonomic.
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·12時間前Type inference is a pretty big thing in TypeScript as well though. In fact it’s probably the biggest thing about it, IMO.
minus-squarecalcopiritus@lemmy.worldlinkfedilinkarrow-up1·8時間前I don’t know typescript. But if that’s the case, this meme doesn’t make much sense. Who writes the types of variables in a language with type inference unless forced by the compiler?
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·5時間前Maybe it’s a language without type interference? Either way, it sometimes makes sense in TypeScript to help the type system out a little bit. let array: string[] = []; In this situation, the type system can’t infer that the empty array should be a string array, because there are no items to go by.
minus-squarenebeker@programming.devlinkfedilinkEnglisharrow-up7·21時間前let a = String::from(“Hello, world!”).into() I’ll see myself out.
It’s also valid rust syntax.
But if it were rust, this meme would not make sense, since you would just type
let a
and type inference would do its thing. Which is much more ergonomic.Type inference is a pretty big thing in TypeScript as well though. In fact it’s probably the biggest thing about it, IMO.
I don’t know typescript. But if that’s the case, this meme doesn’t make much sense.
Who writes the types of variables in a language with type inference unless forced by the compiler?
Maybe it’s a language without type interference?
Either way, it sometimes makes sense in TypeScript to help the type system out a little bit.
let array: string[] = [];
In this situation, the type system can’t infer that the empty array should be a
string
array, because there are no items to go by.let a = String::from(“Hello, world!”).into()
I’ll see myself out.
At least be fair and cut out the
.into()