@lbljeffmo @awbjs @stefanpenner but you can't actually describe that so it's easy to mess it up.
-
-
@wycats similar to how you won't be able to describe a private prop that should be owned entirely by the instance@awbjs@stefanpenner -
@lbljeffmo@awbjs@stefanpenner it's owned by the IMPL not the instance. Feature not a bug. -
@wycats depends who you ask :) I don't see an alt. sol'tn for bin-methods...but it smells of non-locality issues@awbjs@stefanpenner -
@lbljeffmo@awbjs@stefanpenner how so? The code is local. -
@wycats 1/ I don't think this is a fatal issue (assuming realm safety), but I'm disturbed that my pvt property for@awbjs@stefanpenner -
@wycats 2/ an inst is accessible to other insts@awbjs@stefanpenner -
@wycats 3/ and "only if you actually do that" answers seem tautological@awbjs@stefanpenner -
@lbljeffmo@awbjs@stefanpenner there is a huge diff between code that created a variable accessing it and public properties. - 9 more replies
New conversation -
-
-
@lbljeffmo@awbjs@stefanpenner you can never have two fields that can only be changed atomically by the impl. You want that.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.