HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · 6 months agoWhy make it complicated?lemmy.mlimagemessage-square14linkfedilinkarrow-up10arrow-down10file-text
arrow-up10arrow-down1imageWhy make it complicated?lemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · 6 months agomessage-square14linkfedilinkfile-text
minus-squarenebeker@programming.devcakelinkfedilinkEnglisharrow-up0·6 months agolet a = String::from(“Hello, world!”).into() I’ll see myself out.
minus-squareanton@lemmy.blahaj.zonelinkfedilinkarrow-up0·6 months agoAt least be fair and cut out the .into()
minus-squarenebeker@programming.devcakelinkfedilinkEnglisharrow-up0·6 months 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-squareHaradion@lemmy.mllinkfedilinkarrow-up1·6 months agoIf type constraints later in the function let the compiler infer the type, this syntax totally works.
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.
If type constraints later in the function let the compiler infer the type, this syntax totally works.