`core` might confuse proc macros about anchor HOT 3 CLOSED

Hi! 🙂

I forgot about the core crate; definitely wouldn't want to have name conflicts with it. I'm thinking about changing the module name to game as it mostly contains functionality related to the game loop. 🤔

from anchor.

Hi it was misinformation. Sorry. The following code worked without any issue:

use anchor::core;

struct HelloWorld;

impl ::core::fmt::Debug for HelloWorld {
    fn fmt(&self, f: &mut ::core::fmt::Formatter<'_>) -> ::core::fmt::Result {
        write!(f, "Hello, world!")
    }
}

fn main() {
    println!("{:?}", HelloWorld);
}

https://github.com/toyboot4e/core_does_not_conflict/blob/main/src/main.rs

Maybe the last proc macro I saw was using core, not ::core?

from anchor.

Ended up changing the name to game. Although it wouldn't necessarily cause issues with proc macros, it makes importing items from the core crate more difficult, e.g. use ::core::num::NonZeroU8; instead of use core::num::NonZeroU8;.

from anchor.