You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the documentation you're looking for a real-world example, and here I have one. Condensed it looks like this (and you guess right if you think this is actually related to FFI under the hood).
I have a struct
struct Foo {
imp: Box<FooImp>,
}
and a trait
traitFooImp: mopa::Any{// things in here}
The use case here is that Foo is a generic thing with exchangeable implementation, but I want it to be with dynamic dispatch and not generic for reasons (if needed I can explain).
Now all fine so far, but Foo is actually always passed around as an Arc<Foo>, and it's possible to connect "notifications" to Foo
In the documentation you're looking for a real-world example, and here I have one. Condensed it looks like this (and you guess right if you think this is actually related to FFI under the hood).
I have a struct
and a trait
The use case here is that Foo is a generic thing with exchangeable implementation, but I want it to be with dynamic dispatch and not generic for reasons (if needed I can explain).
Now all fine so far, but
Foo
is actually always passed around as anArc<Foo>
, and it's possible to connect "notifications" toFoo
Now a
FooImp
implementation might want to connect to some notification. But it wants to get access to itself again somehow. Here we need mopa:The text was updated successfully, but these errors were encountered: