Sven Kanoldt

@nagisa symbol alias sounds interesting, then also multiple `#[export_name]` attributes must be supported, and `#[no_mangle]` would become a shortcut just as you described it. Is there already an RFC or...

I guess I found the pre-RFC: https://internals.rust-lang.org/t/pre-rfc-defining-function-aliases/11424

The unused attribute lint sounds also reasonable. Would it then be possible to indicate how to fix it and elaborate on the details as well?

I refactored according to the suggestions, but now the test fails as if the lint is not emitted at all anymore. Probably I just miss something, on the registration part.

@CryZe good question, I'm going to add a test for it, but I suspect it doesn't.

@CryZe it works for `#[unsafe(no_mangle)]` but, The error message I would want should be this: ``` warning: the `#[unsafe(no_mangle)]` attribute may not be used in combination with `#[export_name]` ``` But...

I'm stunned, do you have an example repo that causes this to happen?

I ran ```sh cargo generate https://github.com/TheBevyFlock/bevy_new --name foobar1 ``` and had no issues at all. Not sure if there is anything wrong nor if we can do something about it.

Thanks for the Bug report. Just for curiosity: - have you tried to install it via `cargo install --locked cargo-generate` - what `cargo --version` you are running? - Is it...

From the attached build log, I can read one particular issue: ```raw ld: warning: object file (/var/folders/vt/y6dxp8tn2hn8qm1k813dq5lr0000gv/T/rustcmyIHcT/liblibgit2_sys-948b0e06a41415a4.rlib[112](f0f7908ee800b4e1-fs_path.o)) was built for newer 'macOS' version (14.2) than being linked (13.0) ``` This...