> On Feb 12, 2018, at 10:05 PM, Daniel Heidinga
> wrote:
>
> > That said, what side-effects are you concerned about? My claim is that
> > re-resolution in this scenario would not, for example, trigger any class
> > loading or bootstrap invocations.
>
> The
> On Feb 12, 2018, at 6:51 PM, David Holmes wrote:
>>> But I, for one, prefer a "user pays" scheme over an "everyone pays" scheme
>>> (which is what disallowing duplicates would also be).
>> It’s an awkward situation, experience suggests this type of thing bites back