[OT] Modules dropped out of C++17

[Kagamin via Digitalmars-d]

On Tuesday, 9 June 2015 at 09:06:38 UTC, Ola Fosheim Grøstad 
wrote:
> but a problem for structural/duck-like typing when you scale up.

Not a problem of cognitive complexity, though.

On Tuesday, 9 June 2015 at 10:16:12 UTC, Ola Fosheim Grøstad 
wrote:
> When reading code I don't want to wonder if 
> "libraryobject.print()" is a function that is part of an 
> external library or if it is application code. I want that to 
> be clear when skimming over the source. No IDE can help with 
> that without adding clutter.

Not sure how physical layout of source code affects understanding 
of "libraryobject.print()".

> Subclassing is usually the better option.

In statically typed languages you don't control types you receive 
from 3rd party code.