@lbljeffmo @awbjs @stefanpenner it's owned by the IMPL not the instance. Feature not a bug.
-
-
Replying to @wycats
@wycats depends who you ask :) I don't see an alt. sol'tn for bin-methods...but it smells of non-locality issues@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@awbjs@stefanpenner how so? The code is local.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats 1/ I don't think this is a fatal issue (assuming realm safety), but I'm disturbed that my pvt property for@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@wycats 2/ an inst is accessible to other insts@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@wycats 3/ and "only if you actually do that" answers seem tautological@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@awbjs@stefanpenner there is a huge diff between code that created a variable accessing it and public properties.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats 1/ Data is created per-inst. Logic is created per-class. Logic with access to non-this-inst data@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@wycats 2/ can still mess up in a non-local way. Logic with access to only this-inst data can only mess up@awbjs@stefanpenner1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@wycats 3/ locally (repeatedly locally given many insts sure, but narrowing the path from start to bug is smaller).@awbjs@stefanpenner2 replies 0 retweets 0 likes
@lbljeffmo @awbjs @stefanpenner let's talk next week :) twitter ceasing to be beneficial :)
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.