lysdexic@programming.dev to Rust@programming.devEnglish · 1 year agoCommon Rust Lifetime Misconceptions (2020)github.comexternal-linkmessage-square5fedilinkarrow-up138arrow-down11cross-posted to: hackernews@derp.foo
arrow-up137arrow-down1external-linkCommon Rust Lifetime Misconceptions (2020)github.comlysdexic@programming.dev to Rust@programming.devEnglish · 1 year agomessage-square5fedilinkcross-posted to: hackernews@derp.foo
minus-squarehairyballs@programming.devlinkfedilinkarrow-up1·edit-21 year agoThere are still obvious things the BC cannot get. For example: struct Foo; impl Foo { fn num(&mut self) -> usize { 0 } fn index(&mut self, _i: usize) { } } let foo = Foo; foo.index(foo.num()); //error
minus-squaresirdorius@programming.devlinkfedilinkarrow-up2·edit-21 year agoThis looks like a pretty easy fix that the compiler could do by extracting the argument to a temp variable to improve the syntax of the language.
minus-squareKillTheMule@programming.devlinkfedilinkarrow-up1·edit-21 year agoNote that when you change num to take &self instead, this works out (you also need to mark foo as mutable, of course).
minus-squarehairyballs@programming.devlinkfedilinkarrow-up1·1 year agoIt’s a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.
There are still obvious things the BC cannot get. For example:
struct Foo; impl Foo { fn num(&mut self) -> usize { 0 } fn index(&mut self, _i: usize) { } } let foo = Foo; foo.index(foo.num()); //errorThis looks like a pretty easy fix that the compiler could do by extracting the argument to a temp variable to improve the syntax of the language.
Note that when you change
numto take&selfinstead, this works out (you also need to markfooas mutable, of course).It’s a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.