On Tue, May 5, 2015 at 7:10 PM, Valentin Gosu <valentin.g...@gmail.com> wrote: > On 6 May 2015 at 04:58, Doug Turner <do...@mozilla.com> wrote: >> > On May 5, 2015, at 12:55 PM, Jonas Sicking <jo...@sicking.cc> wrote: >> > >> > On Thu, Apr 30, 2015 at 3:34 PM, Valentin Gosu <valentin.g...@gmail.com> >> > wrote: >> >> As some of you may know, Rust is approaching its 1.0 release in a >> >> couple of >> >> weeks. One of the major goals for Rust is using a rust library in >> >> Gecko. >> >> The specific one I'm working at the moment is adding rust-url as a >> >> safer >> >> alternative to nsStandardURL. >> > >> > Will this affect our ability to make nsStandardURL thread-safe? > > Unfortunatelly this project does not make nsStandardURL thread safe.
Sorry, I think you misunderstand my question. I definitely don't suggest that you should do *anything* to improve the threadsafetyness of nsStandardURL as part of using Rust to implement it. I.e. I'm not asking you to add threadsafe addref/release, improve any addon APIs, remove the nsIURI mutators, or do any of the other things that are needed to make it possible to use nsStandardURL off the main thread. What I'm asking is that when *someone else* has fixed the various issues that currently prevent us from using nsStandardURL off the main thread, will the fact that nsStandardURL is implemented in Rust make it troublesome for us to use nsStandardURL from multiple threads? Or can the Rust code be called from multiple threads simultaneously without causing race issues? / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
