Closed anth0nyleung closed 10 months ago
This is actually unrelated to the env
issues I've been having lately (which are due to issues with spans of some builtin macros). This is due to not using postgrestd, which has some extra hacks to make the include macro get detected.
Can you try with something like:
RUSTFLAGS="-Wplrust_lints -Aplrust_external_mod -Aplrust_print_macros" RUSTC=plrustc cargo check --target=x86_64-postgres-linux-gnu
That is, add --target=x86_64-postgres-linux-gnu
(or another postgrestd target that works on your machine) to the invocation.
I've tested it myself and can confirm this fixes it. Reopen if it doesn't for you.
Thanks! I tested it on my set up and adding the target flag solves the issue
Issue
plrustc has a lint to catch for filesystem macros and env macros, like
include_str!
,include_bytes!
,env!
andoption_env!
. It appears that the linter is not catching theinclude!
macro usage properly.Repro
and
https://github.com/rust-num/num-bigint/blob/num-bigint-0.4.4/src/biguint/convert.rs#L795