-
-
Replying to @jimblandy
@wycats But perhaps I should have noticed that both on Twitter and in RFCs, "functional" generates quite a lot of heat per illumination.1 reply 0 retweets 0 likes -
Replying to @jimblandy
@jimblandy linear(ish) types solve a fundamentally functional problem without sacrificing performance.1 reply 0 retweets 0 likes -
Replying to @wycats
@jimblandy functional impls are ALWAYS allowed to do global mut as long as it can prove nobody cares. Rust gives those tools to everyone.1 reply 0 retweets 0 likes -
Replying to @wycats
@jimblandy consider fn foo(self, val: u32) -> T { self.x = val; self } ; functional style with mutation as impl detail2 replies 0 retweets 0 likes -
Replying to @jimblandy
@jimblandy what problems of in-place mutation is functional style trying to address?1 reply 0 retweets 0 likes -
Replying to @jimblandy
@wycats But by threading state arguments into and out of functions, we can turn any single-threaded imperative code into functional code.1 reply 0 retweets 0 likes -
Replying to @jimblandy
@wycats So I feel if we accept x.f() mutating x as equiv to passing x and then receiving a new x on the way out, we've given up too much.1 reply 0 retweets 0 likes
@jimblandy in order to make state threading work universally, we have to make the fields of the data structure public, which is costly too.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.