They’re not the same class and that’s the problem. It’s similar to loading two versions of the same library in OSGi and allowing the two classes to get mixed up somehow (fun errors like Foo is not type Foo), typically a bug.
On Fri, Jul 24, 2020 at 11:30 Gilles Sadowski <[email protected]> wrote: > Le ven. 24 juil. 2020 à 17:46, Matt Sicker <[email protected]> a écrit : > > > > Shading also violates a lot of common ClassLoader assumptions like not > > having multiple copies of the same class in the same visible context > (even > > if different packages) > > How classes in different packages could be the same class? > > Gilles > > > [...] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Matt Sicker <[email protected]>
