-
-
Replying to @stefanpenner2 replies 0 retweets 0 likes
-
Replying to @stefanpenner
@stefanpenner kinda.. Still possible for an inst to make rounds through a program and back to a mutative method unexpectedly@awbjs@wycats1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@stefanpenner@wycats how so? Only if you write a method that intentionally mutates private state of an argument.1 reply 0 retweets 0 likes -
Replying to @awbjs
@awbjs that's right. Just like encap'd public props are only a hazard of you write logic to inten'ly interact w/ them@stefanpenner@wycats2 replies 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@awbjs@stefanpenner what's an encapsulated public property?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats (140chars) A public prop not meant to be read from outside@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@awbjs@stefanpenner but you can't actually describe that so it's easy to mess it up.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats similar to how you won't be able to describe a private prop that should be owned entirely by the instance@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@awbjs@stefanpenner it's owned by the IMPL not the instance. Feature not a bug.2 replies 0 retweets 0 likes
@lbljeffmo @awbjs @stefanpenner iow, you know which code changes the slot. It's in the same file. Diff from pub fields.
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.