Zach Oakes

@Deraen Yes, that is how I currently do it, but this particular issue was spurred by my use of deps.edn (see the first comment on [my gist](https://gist.github.com/oakes/778de5ca7fd1a764829bcab14a1c42a9)), which doesn't directly...

Is this still a work in progress? I just ran into the problem today.

Is there a fundamental problem with unboxed closures that requires boxed closures to be used instead? I don't know enough about Rust internals to understand what the problem is.

That makes sense; I'm just surprised it ends in a segfault, but I suppose that's the nature of FFI. I don't think top-level functions would work for me, because my...

I need to create several signal handlers, all of which having access to the same values, so I don't think I can use `move`.

I can wrap the values I intend to use in reference-counted cells, but it doesn't solve the primary issue, which is that I have several signal handlers that need them,...

Thanks for the tip, I am currently trying it out. I made a handler creation function just like yours, and cloned the Rc objects, but on the very first `borrow_mut`...

That's the puzzling thing -- it's the very first time `borrow_mut` is called. Perhaps it's because I'm not using boxed closures, though; I'm doing `button.connect(gtk::signals::Clicked::new(&mut move || { ... }));`....

Sure, [here's](http://pastebin.com/6N4NP9Qs) the part I'm working with right now. It's using my fork of rgtk to create a `Box` containing a `VteTerminal` with several buttons corresponding to cargo commands.

Yeah I figured that would be a problem. I may have to revisit this later, as it is proving really difficult.