Consider removing support for paths in `abigen!` in favour of Rust's `include_str!` about fuels-rs HOT 6 CLOSED

Just been taking a look into this issue with @mitchmindtree. Unfortunately, I don't think rust will let us expand an expression given to the second argument into a string at the time of procedural macro expansion. grrrrr shakes fist at rust

Perhaps another solution is to find the logic that include_str! is doing and copy that over as a function instead. I'll see if I can track down what code is actually being called internally.

from fuels-rs.

Love this idea, let's do it!

from fuels-rs.

Damn you Rust!

But yeah, fair enough, #97 sounds like a good option too.

from fuels-rs.

Yeah 🤦

Unfortunately it looks like we can't evaluate an expression given to the second argument to a string that we can actually use to generate the Contract type during proc macro expansion. I imagine that might be why abigen! is the way it is now!

There's some writing on this limitation on expanding macros in argument position of other macros here.

Barring that, I think @JoshuaBatty's suggestion of modelling our "path" source behaviour after include_str! is a good idea. I'll close this and open another dedicated issue.

from fuels-rs.

This may also solve #93 as a side effect.

from fuels-rs.

True, include_str! should work on multiple platforms... Very nice side effect 😁

from fuels-rs.