jezza / def_mod Goto Github PK

Github repository lacks some metadata.

Should be something like

a Rust proc macro allows to forward-declare a module interface and route it to specific implementation depending on cfg.

Now, as I write this, I honestly believe it's not possible...
At least, not without a great deal of work.

I think the solution would, at the very least, involve a compiler plugin, but there's definitely some things that are working against us here.

First hurdle:
We need to look at what things a module exports.
Now, in a very simple case, we could just look at the file, inspect the contents, and determine what types and methods it exported.
Programmatically, of course.

Where things start getting difficult is when it's more complex than just exporting a type that was declared in the module.
What if someone exports a type from a library?
And that library isn't available on the given system, because it's on a different os?

Honestly, I think it's not possible simply due to how... well, logic works.
I can't access and inspect something that isn't there...

There's definite solutions that get us halfway, such as the aforementioned scraping, but that's going to be nothing more than superficial at best.

If anyone has any ideas about how to implement this nicely, or I've misunderstood accessibility, please do chime in.