HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-27 days agoWhy make it complicated?lemmy.mlimagemessage-square122fedilinkarrow-up1365file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up1365imageWhy make it complicated?lemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-27 days agomessage-square122fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squarenebeker@programming.devlinkfedilinkEnglisharrow-up8·7 days agolet a = String::from(“Hello, world!”).into() I’ll see myself out.
minus-squareanton@lemmy.blahaj.zonelinkfedilinkarrow-up4·6 days agoAt least be fair and cut out the .into()
minus-squarenebeker@programming.devlinkfedilinkEnglisharrow-up3·6 days 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·3 hours 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.