An unsafe block is considered an invalid expansion, even though its contents form a valid expression

[ramonacat]

There's also the second error, which I honestly don't fully understand as I use paths starting with :: all over the place, and only this one has issue.

   Compiling eisheth v0.1.0 (/home/ramona/Projects/ligeia/eisheth)
error: Potentially invalid expansion. Expected an expression, an identifier, `::`, `<`, `Self`, `break` or 13 others.
  --> eisheth/src/module/macros.rs:70:21
   |
70 |         let $name = unsafe {
   |                     ^^^^^^

error: Potentially invalid expansion. Expected an identifier, `Self`, `_`, `self`, `super`, a `(`.
  --> eisheth/src/module/macros.rs:94:31
   |
94 |             $($function_name: ::eisheth::module::DeclaredFunctionDescriptor),*
   |                               ^

error: could not compile `eisheth` (lib) due to 2 previous errors

code: ramonacat/ligeia@df5c26b#diff-77bcda3d388bae57442da72490152305ad8871346955e17ed968cb18d2323217

[scrabsha]

Hi there! I am slowly adding support for more and more of the Rust syntax to expandable. Most importantly, there is no support for unsafe blocks and ::-prefixed paths yet :/

While adding support for these two syntax things is doable (you can almost do yourself actually 😅), I'm trying to go toward a more general solution that would allow me to support all the Rust syntax at once, without requiring me to write a full Rust parser by hand.

If you care about this specific problem to be fixed, I can probably mentor you, but it's likely you'll hit another "unsupported syntax problem" right after.

Meow