On Tue, 21 May 2024 20:14:41 GMT, Jorn Vernee <jver...@openjdk.org> wrote:
>> Class loading triggered by `Class.forName()` call is at the core of >> `isTypeVisible`. (The rest is fast path checks.) It's what makes >> `isTypeVisible` query idempotent. >> >> I can definitely name it differently (e.g, `ensureTypeVisible`), but making >> a separate class loading pass across signature classes doesn't make much >> sense. > >> I can definitely name it differently (e.g, ensureTypeVisible), but making a >> separate class loading pass across signature classes doesn't make much sense. > > Ok, in that case I suggest also renaming `MemberName::checkForTypeAlias`, > maybe to `ensureTypeVisible` as well. @JornVernee ok, renamed. ------------- PR Comment: https://git.openjdk.org/jdk/pull/19319#issuecomment-2145967665
