implementation where?

[xiaguangbo]

esp-hal/src/soc/mod.rs:

pub use self::implementation::*;

#[cfg_attr(esp32, path = "esp32/mod.rs")]
#[cfg_attr(esp32c2, path = "esp32c2/mod.rs")]
#[cfg_attr(esp32c3, path = "esp32c3/mod.rs")]
#[cfg_attr(esp32c6, path = "esp32c6/mod.rs")]
#[cfg_attr(esp32h2, path = "esp32h2/mod.rs")]
#[cfg_attr(esp32s2, path = "esp32s2/mod.rs")]
#[cfg_attr(esp32s3, path = "esp32s3/mod.rs")]
mod implementation;

implementation where? I can't find

[Dominaezzz]

path = is what you're looking for

[Dominaezzz]

It's in the code snippet you pasted 🙂

[Dominaezzz]

https://doc.rust-lang.org/reference/items/modules.html#the-path-attribute

[xiaguangbo]

in the esp-hal/src/soc/esp32.../mod.rs? but i no final, I wondered...

[xiaguangbo]

Is implementation just a placeholder name? As long as I modify both pub use self::implementation::; and mod implementation; simultaneously, there won't be any issues? For example, changing them to pub use self::abc::; mod abc; without modifying the esp32.../mod.rs files?
I did not find like pub mod implementation {...}.

[bugadani]

You know how this works:

mod my_module; // my_module will be created from either my_module/mod.rs, or my_module.rs

If there is path = ... on top of the module, that will tell the compiler which file to use to create my_module.

Here we have 7 different files, depending on the MCU. The compiler will create mod implementation from one of those files.