make_static -> mk_static?

[yanshay]

A bit off topic, but important for development of async apps:

I upgraded from rustc 1.80 to 1.82, and face the collapse of make_static!.
mk_static! which is provided in several examples can fill in in most cases but:

1. Sometimes it's very difficult to tell the type in case of deep and complex inferred generics.
2. Sometimes I believe it's impossible (picoserve types seems to me to be impossible due to types generated from function calls, I couldn't understand what they are doing there).

I've seen the comment above the mk_static in the code here (see below).

a. Is there a way to get make_static to work using nightly compiler? I thought this is already the nightly compiler with esp toolchain.
b. Is there an easy way to tell a concrete type in case of complex generics? In some cases I need to dive deep into sources and follow the generics, I still struggle with one case. The compiler knows it, so is there a way to get it to tell me? (RustAnalyzer provides some information but it's not always complete)

// When you are okay with using a nightly compiler it's better to use https://docs.rs/static_cell/2.1.0/static_cell/macro.make_static.html

macro_rules! mk_static {
    ($t:ty,$val:expr) => {{
        static STATIC_CELL: static_cell::StaticCell<$t> = static_cell::StaticCell::new();
        #[deny(unused_attributes)]
        let x = STATIC_CELL.uninit().write(($val));
        x
    }};
}

[bugadani]

it, so is there a way to get it to tell me?

Just use () first, then the compiler will tell you that it is wrong and will give you the correct type.

[yanshay]

Thanks! that worked.

Moving on to new compilation problems with picoserve around opaque type's declaration issues in &'static parameters to embassy task...

I didn't think upgrading minor rust versions could lead to compilation issues.

[bugadani]

Using nightly features is always a risk. This time, taking that risk with TAITs didn't pay off.