Deprecate optional parentheses for zero-argument function calls

[whitebyte]

I'm pretty sure this will go nowhere, but anyway.
Consider deprecating optional parentheses for zero-argument function calls. This is an unfortunate design choice, because it introduces hidden control flow, and hidden control flow is bad

class MyClass {
    int length() {
        // here I will do nasty things. Side effects, memory allocations etc
        // and, as a cherry on top:
        throw new Exception("You want integer? Too bad, here grenade!");
    }
}

auto x = new MyClass();
writeln(x.length); // <- looks completely innocent
writeln(x.length()); // <- here it's clear that I have a function call, not just member access

[adamdruppe]

Would introduce waaay too much breakage. And if you follow the logic, this also would would eliminate operator overloads and destructors and properties and anything else that hides a function call.

[Kapendev]

It's not exactly hidden control flow, though. If you're unaware that something is a function, that's ultimately your responsibility. Maybe better names can also help with this.
And hidden control flow is not bad. What about slices? Should we write items.getItemWithBoundCheck(0)?