[Help] proc macros hiding error information

[ToxicMushroom]

Do you know of an approach to debug errors such as these ?

error[E0502]: cannot borrow value as mutable because it is also borrowed as immutable
   --> src/tui/mod.rs:275:1
    |
275 | #[component]
    | ^^^^^^^^^^^^
    | |
    | mutable borrow occurs here
    | immutable borrow occurs here
    | immutable borrow later used here
    | in this attribute macro expansion
    |
   ::: /home/merlijn/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/iocraft-macros-0.2.3/src/lib.rs:648:1
    |
648 | pub fn component(_attr: TokenStream, item: TokenStream) -> TokenStream {
    | ---------------------------------------------------------------------- in this expansion of `#[component]`

I've had other cases like this with lifetimes and references but was able to solve those in the end.

[ToxicMushroom]

This seems caused by the lifetimes I added in the calculator example as such:
fn Calculator<'a>(mut hooks: Hooks<'a, '_>) -> impl Into<AnyElement<'a>> {

[ccbrown]

Hmm... unfortunately I don't really have a great approach for you. I think a lot of it just comes from intuition and trial/error unfortunately.

In the case of your calculator example, try taking the explicit lifetime away from Hooks:

fn Calculator<'a>(mut hooks: Hooks) -> impl Into<AnyElement<'a>> {

I don't know of any use-case where an explicit lifetime on Hooks is needed.

If you can provide other examples, I can try to help, and if we start to compile all the common types of lifetime issues, I can potentially make the macro give more helpful output for common mistakes. E.g. for the calculator example, the macro could suggest removing the lifetime from Hooks.

[ToxicMushroom]

Thanks for your response :)

The lifetime was required for a lifetime on one of my context parameters which were constructed from a reference. However, I realized I needed mutability shortly after, I then switched to an Arc Mutex but I forgot to revert the lifetime on the Hook type.

I'll try to create a sensible example use-case next week