search for: linkdefinedtypebodies

...'". 3) inlinining loads module "b", clones it, links module "b'" into "main1'". This module has a *non-opaque* definition of "t". Thus "t", as referenced by "main1'", gets its type "t" completed (via linkDefinedTypeBodies()). 4) "main2" module gets created 5) inlining clones module "a". As types are global to a context, "t" now has a body, *and* the body appears to be from the source module (actually "b'"). "mapping to a source type" is the result. As far...

...3) inlinining loads module "b", clones it, links module "b'" into > "main1'". This module has a *non-opaque* definition of "t". Thus "t", > as referenced by "main1'", gets its type "t" completed (via > linkDefinedTypeBodies()). > 4) "main2" module gets created > 5) inlining clones module "a". As types are global to a context, "t" now > has a body, *and* the body appears to be from the source module > (actually "b'"). "mapping to a source type" is th...

...loads module "b", clones it, links module "b'" into > > "main1'". This module has a *non-opaque* definition of "t". Thus "t", > > as referenced by "main1'", gets its type "t" completed (via > > linkDefinedTypeBodies()). > > 4) "main2" module gets created > > 5) inlining clones module "a". As types are global to a context, "t" now > > has a body, *and* the body appears to be from the source module > > (actually "b'"). "mapping to a sou...

...module "b", clones it, links module "b'" into >>> "main1'". This module has a *non-opaque* definition of "t". Thus "t", >>> as referenced by "main1'", gets its type "t" completed (via >>> linkDefinedTypeBodies()). >>> 4) "main2" module gets created >>> 5) inlining clones module "a". As types are global to a context, "t" now >>> has a body, *and* the body appears to be from the source module >>> (actually "b'"). "mappin...