Re: Implementing a Chrome DevTools Protocol server in Firefox

> I entirely agree that the current Firefox protocol is also proprietary. > However I also assumed that it's considered an internal implementation > detail rather than something we would expect people to interoperate with. If > that wasn't the case then I apologise: I should have complained

Re: New minimum Rust version policy for Firefox

Specifically for webrender (and anything else under the servo org on GitHub), you can just file a bug and assign to edunham and we'll fix that up. jack. On Thu, Aug 31, 2017 at 10:25 AM, Kartikaya Gupta wrote: > Do we have a policy on CI coverage for vendored rust libraries?

Re: Editing vendored crates take #2

There is this bug which the Cargo team is planning to work on to help with these problems, but it hasn't been implemented yet that I know of. https://github.com/rust-lang/cargo/issues/2649#issuecomment-279615299 jack. On Fri, Apr 28, 2017 at 11:28 AM, Bobby Holley wrote:

Re: Quantum Flow Engineering Newsletter #5

different hardware profiles. jack. On Tue, Apr 18, 2017 at 5:22 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > On 2017-04-18 1:53 PM, Justin Dolske wrote: >> >> >> On Tue, Apr 18, 2017 at 1:19 AM, Jack Moffitt <j...@metajack.im >> <mailto:j...@metajack

Re: Quantum Flow Engineering Newsletter #5

> Another really nice effort that is starting to unfold and I'm super excited > about is the new Photon performance project > , which is a focused > effort on the front-end performance. This includes everything from > engineering the new UI

Re: Should cheddar-generated headers be checked in?

I think running bindgen at build time will be the best practice. That is certainly what stylo and the spidermonkey bindings are aiming for. This capability of bindgen is pretty new, so it will take a while before the Rust community adapts. jack. On Wed, Feb 22, 2017 at 8:49 AM, Ted Mielczarek

Re: Notes about implementing DOM APIs in Rust

> I do not recall dismissing exposing COM-compatible vtables from Rust. We must implement COM interfaces in Rust for Windows platform things* already. Specifically I have macros that generate IUnknown which for Windows COM includes AddRef, Release, and QueryInterface. For COM interfaces with

Re: Proposed W3C Charter: Web Performance Working Group

Many of the proposed output specifications for this seem quite useful for the kinds of work we are doing in Servo. While this is aimed at web developers, it seems very useful for browser vendors to be measuring things the same way. Having standard ways of doing this means we'll be able to get more

Re: Intent to Use Counter: Everything

We have the Chrome popularity data, and we have the Edge team's data which covers the CSS spectrum quite well. I think it would be far more useful to start covering the DOM API spectrum. For example, it's pretty clear from existing data sources which CSS properties Servo should focus on. But we

Re: Static analysis for "use-after-move"?

, Apr 27, 2016 at 6:04 PM, Jack Moffitt <j...@metajack.im> wrote: > On Wed, Apr 27, 2016 at 5:29 PM, Kyle Huey <m...@kylehuey.com> wrote: >> Can we catch this pattern with a compiler somehow? > > Yes. Example: > > foo.rs: > > struct Foo { > x: u64, >

Re: Static analysis for "use-after-move"?

On Wed, Apr 27, 2016 at 5:29 PM, Kyle Huey wrote: > Can we catch this pattern with a compiler somehow? Yes. Example: foo.rs: struct Foo { x: u64, } fn do_bar(foo: Foo) { } fn main() { let foo = Foo { x: 0, }; do_bar(foo); if foo.x == 0 {

Re: Linux distro readiness for Rust in Gecko

> I've been assuming that Firefox would use the Rust "stable" channel > compiler on the Firefox "release" channel, but I don't know if that > has ever been really *decided* anywhere. Has it been decided? Your assumption is correct. For gecko integration related work we use the stable version of

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

> On the other hand, in that same thread, metajack said, "The current plan is > to have Rust (in the form of rust-url replacing nsUrlParser) riding the > trains later this quarter." And indeed, Rust is now riding the trains with the moov parser. It's not required for the build yet, but Nightly