Alternatives for naming automatic modules, and a proposal (#AutomaticModuleNames)

[Brian Fox]

On Mon, Apr 24, 2017 at 12:14 PM, <mark.reinhold at oracle.com> wrote:

> The problem with any approach that allows you to give a stable name to
> what is otherwise an automatic module is that the API of that module is
> inherently unstable.  If and when the module is completely modularized
> then its API will almost certainly change, which in turn will require
> incompatible changes to any previously-published fully-modularized
> modules that depend upon it.
>

I don't quite follow, why does modularizing a module imply its public api
will change?