Simonas Kazlauskas

It would be fairly difficult to provide anything more than text fields and buttons in a way such that all the functionality is exposed.

Interesting. I cannot reproduce the error on Linux and do not possess an OS X machine to test this on, so I can’t really help debugging this other than with...

Interesting places to start tracking down the issue would be a stack trace at the time of hardware fault and disassembly around the invalid insn, I guess.

Hmm, at a first sight it probably has nothing to do with the implementation of this library. Rather, Rust (and all other languages’) programs have some thread local storage set...

According to @alexcrichton, it is very likely to be a case of the library registering some TLS destructors with pthreads, but they’re executed only when the thread itself finishes, rather...

I’m not aware of any issues reported in other projects, nor I am aware of a public OS X issue tracker of any sort where such an issue could be...

@calebmer sorry for the late response! Your comment completely fell through the cracks! Your’s are all very good questions thus I’ll try to answer them extensively: > If this is...

@emoon I guess the least intrusive way _stable_ way currently would be to do something like this and then wrap your `Library` into the `Leak`. ``` rust struct Leak(Option); impl...

> if I understand correctly it's an issue with the way the Rust compiler generates dylibs. There’s nothing specific with the dylib generation, but rather with how Rust standard library...

Since 0.3 you [can specify arbitrary flags](https://docs.rs/libloading/0.3.0/libloading/os/unix/struct.Library.html#method.open) when opening a library. The `RTLD_NODELETE` (thanks for reminder @Np2x) essentially acts as implicit `mem::forget` so you can now do something along the...