Injector.jl uses a bit of a hack to figure out the module name of where a stack frame is coming from: it looks at the path. Surely there's a better way?
At any rate, it doesn't account for locally-installed modules which is a pattern we'll almost certainly want to accommodate.
Injector.jl uses a bit of a hack to figure out the module name of where a stack frame is coming from: it looks at the path. Surely there's a better way?
At any rate, it doesn't account for locally-installed modules which is a pattern we'll almost certainly want to accommodate.