On Friday, 26 July 2013 at 13:11:33 UTC, JS wrote:
But what about protection semantics? Access to this? Properties? Virtual functions?
Non-public methods should not be free functions. Same goes for virtual ones. Access to this is no different from access to first parameter of function.
That still leaves tons of utility stuff people usually implement as methods despite the fact they don't really need to be ones.
