| 00:41 | <Kris Kowal> | I sketched guybedford (Guy Bedford) and Luca Casonato ’s ModuleInstance in the context of the Loader née Compartments proposal https://github.com/tc39/proposal-compartments/pull/51 |
| 00:42 | <Kris Kowal> | In short, it doesn’t obviate the need for Loader, because dynamic import has to fall through. |
| 00:42 | <Kris Kowal> | It may be interesting to include a ModuleInstance constructor regardless, but it doesn’t reduce the scope of the Loader proposal. |
| 01:23 | <Kris Kowal> | On further reflection (updated above PR, it’s possible to implement Loader in user code, with all of the “static import” part of Import Reflection, ModuleInstance, and a Global constructor for the hardened JavaScript case. The user-code Loader wouldn’t be able to do import reflection on your behalf, so you’d have to learn harder on that. |
| 01:24 | <Kris Kowal> | The user code loader would have to thread a dynamic import (or not). |