callback execution hell gives many errors at runtime

[JSmithOner]

Summary

I have a callback that get called from a websocket from my browser and I'm using a #[wasm_bindgen] function in an impl that I am calling to retrieve the result inside the Rust environment

my js:

const p = create_peer( );

socket.on( async ( message ) => {

  await p.on_message(  message )

} );

my rust

impl Peer {

  ...

  on_message ( &self ) {

    self.clone().member = some_value;
    ...
    something.await;
    ... 

  }

  ...

}

pub fn create_peer() {

  let peer = Peer::new()

  peer.some_function_that_sends_message_to_web_socket();

}

basically my impl self is referenced into many methods and many operation get triggered asynchronously both on js and rust side.

This is resulting in many errors unreachable or already borrowed or recursive use of object, I would say I'm kinda facing some sort of callback execution hell.

So my question is how can I make sure both environments keeps running the tasks in a manner I don't trigger a function make use of an already borrowed element. How can I keep both environments in sync because all of these errors always show on runtime which make them really hard to debug?

Thanks

ps:if you need more code please tell me.

[dzfranklin]

Hi, I'm not associated with this project but I'm writing similar code to your example. I'm interested in the error you're running into because I want to know if I'll end up with the same problem.

I did a trivial test of a recursive call and didn't run into any errors. I also peeked at the code the macro generates and didn't spot any locking or anything fancy. But I may well have missed something.

Do you have an example I can run that will fail with the error you're getting? (Ideally you'd reduce it to as little code as necessary to get to the error). I'm interested in taking a look.

I also searched this repository for your error messages and got no matches. Can you post the exact full error messages specific code causes?

Unrelatedly self.clone().member = value looks fishy. You're creating a duplicate of self, mutating it, and then throwing it away.

[daxpedda]

This doesn't really look like a wasm-bindgen problem to me, but just a borrowing issue with the Rust language itself.

I'm happy to take a look if you could provide a minimal self-contained example.

[JSmithOner]

@daxpedda No need I've closed the project.Thanks anyway