http://d.puremagic.com/issues/show_bug.cgi?id=8162
art.08...@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |art.08...@gmail.com --- Comment #4 from art.08...@gmail.com 2012-05-30 10:34:21 PDT --- (In reply to comment #1) > If strict property enforcement is implemented, S.opDispatch won't work > anymore. > Because @property is not considered by overload resolution. This is already a problem; i had cases where i couldn't use opDispatch, because i needed both the @property and "method" versions... It would be best if both property and non-property versions would be legal at the same time, at least for opDispatch. This bug has more serious consequences -- think properties that return callables -- 'o.property()' does not do what you expect it to do, instead you have to work-around with 'o.property()()', which doesn't really make sense. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------