HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-22 days agoWhy make it complicated?lemmy.mlimagemessage-square114linkfedilinkarrow-up1362arrow-down136file-textcross-posted to: [email protected]
arrow-up1326arrow-down1imageWhy make it complicated?lemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-22 days agomessage-square114linkfedilinkfile-textcross-posted to: [email protected]
minus-squarecalcopiritus@lemmy.worldlinkfedilinkarrow-up13·2 days agoIt’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-squarenebeker@programming.devlinkfedilinkEnglisharrow-up8·2 days agolet a = String::from(“Hello, world!”).into() I’ll see myself out.
minus-squareanton@lemmy.blahaj.zonelinkfedilinkarrow-up4·1 day agoAt least be fair and cut out the .into()
minus-squarenebeker@programming.devlinkfedilinkEnglisharrow-up3·23 hours agoAnd bow to the compiler’s whims? I think not! This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up1·1 day agoType 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·1 day agoI 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·1 day agoMaybe 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.
It’s also valid rust syntax.
But if it were rust, this meme would not make sense, since you would just type
let aand type inference would do its thing. Which is much more ergonomic.let a = String::from(“Hello, world!”).into()I’ll see myself out.
At least be fair and cut out the
.into()And bow to the compiler’s whims? I think not!
This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.
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
stringarray, because there are no items to go by.