cm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agoUse this information wiselylemmy.todayexternal-linkmessage-square18fedilinkarrow-up1260arrow-down16
arrow-up1254arrow-down1external-linkUse this information wiselylemmy.todaycm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agomessage-square18fedilink
minus-squareanton@piefed.blahaj.zonelinkfedilinkEnglisharrow-up8·edit-24 months agoMy IDE says: '(', '+', '-', '.', ';', <operator>, '[' or '}' expected, got ';' But the rust compiler explains error: unknown start of token: \u{37e} help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not``` what a killjoy.
minus-squareOwl@mander.xyzlinkfedilinkarrow-up6·4 months ago But the rust compiler explains If this is true then rust deserves all the praise it gets
minus-squarebillwashere@lemmy.worldlinkfedilinkEnglisharrow-up0·4 months agoThis is pretty cool. But my question is if the compiler knows it’s basically the same thing visually, why doesn’t it treat it the same way as far as syntax and just make them functionally equivalent;
minus-squarearrowMace@lemmy.worldlinkfedilinkarrow-up1·4 months agoBecause then logically extending this you end up with JavaScript, where “1”==1 and it’s super hard to reason about what will/should happen
My IDE says:
'(', '+', '-', '.', ';', <operator>, '[' or '}' expected, got ';'But the rust compiler explains
error: unknown start of token: \u{37e} help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not``` what a killjoy.If this is true then rust deserves all the praise it gets
This is pretty cool. But my question is if the compiler knows it’s basically the same thing visually, why doesn’t it treat it the same way as far as syntax and just make them functionally equivalent;
Because then logically extending this you end up with JavaScript, where “1”==1 and it’s super hard to reason about what will/should happen