Timothy Lochner

Inheritance and composition are much easier to understand/explain when done with binding/environment explicitly. 7/11

UFCS means you can do all this without having to change a lot of existing code that uses method syntax. 8/11

Since all hypotheses need something predictable to test, here's my prediction. 9/11

With the adoption of UFCS, a valid programming technique will be to forward declare "empty" classes and move all code into functions. 10/11

All that's left is the death of declaration (just resolve all these at link time) and you have... a typed Scheme. :-) 11/11

Privacy and real methods will still have value. But limited. Focused on the data of the class. Bookkeeping would be difficult otherwise.

I.e., preventing raw access to your dynamic array, lest someone forgets to keep the internal count fresh.

In that way, UFCS bothers me as it removes subtle queues about what a function can do or what access it has.