esp-config cannot be used with esp-hal-embassy

[bugadani]

esp-hal's build script errors if users set esp-hal-embassy config options. This is, because esp-hal doesn't know about the other crate, and esp-hal is a prefix of esp-hal-embassy, therefore the crate thinks that ESP_HAL_EMBASSY_ config values belong to it, but rejects them as unknown.

[MabezDev]

Yeah we should fix this ASAP, added to the milestone.

[bugadani]

Any ideas how? :D I guess we can list the conflicting prefixes for esp-hal, but that solution only works as long as we don't create another esp-hal-* crate. Or even worse, someone else creates one - looking at you, community crates.

[bjoernQ]

only thing I can think of (and is breaking) is to have a special separator between the crate name and the config key.

Something like ESP_HAL_EMBASSY_CFG_config - then esp-hal would look for ESP_HAL_CFG_xxx only

and even a crate named esp-hal-cfg would look for ESP_HAL_CFG_CFG_xxx

But it's not ideal

[bugadani]

We can go with two underscores as a separator, I guess. ESP_HAL_CFG__FOO may still not be visually obvious, but it's probably less magical?