Richard Schneeman on Nostr: nprofile1q…480xw if I read this tracking issue correctly, it's currently not ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqxl6v22tg44a3jkymxkd2u2ejh4s497maklu4ccyunt8g5zpjsgkqy480xw (nprofile…80xw) if I read this tracking issue correctly, it's currently not possible to write an `include_str!` macro as the API that provides the caller file path is not exposed https://github.com/rust-lang/rust/issues/54725
Second best option is: Taking a path that's relative to the crate root, which works and you can read the CRATE_MANIFEST_DIR from the env in the proc macro. But it's jarring having to remember which macro uses which root.
Second best option is: Taking a path that's relative to the crate root, which works and you can read the CRATE_MANIFEST_DIR from the env in the proc macro. But it's jarring having to remember which macro uses which root.