Re: The convention to pass a parameter when ownership transfer is optional

2016-03-18 Thread Xidorn Quan
On Fri, Mar 18, 2016 at 11:07 AM, wrote: > > https://hg.mozilla.org/mozilla-central/file/3e04659fdf6aef792f7cf9840189c6c38d08d1e8/mfbt/UniquePtr.h#l182 > > "To unconditionally transfer ownership of a UniquePtr into a method, use a > |UniquePtr| argument. To conditionally transfer ownership of a

Re: Are we in favour of implementing the client hints header?

2016-03-18 Thread Henri Sivonen
On Tue, Mar 8, 2016 at 8:22 AM, Andrew Overholt wrote: > Implement Client-Hints HTTP header > https://bugzilla.mozilla.org/show_bug.cgi?id=935216 Client-Hints is negotation on the HTTP layer that goes beyond reversible bit transformation (i.e. it's not like gzip or Brotli). I continue to believe

Re: Linux distro readiness for Rust in Gecko

2016-03-18 Thread Mike Hommey
On Fri, Mar 18, 2016 at 05:23:21PM +0200, Henri Sivonen wrote: > You say you don't see #5 happening. Do you see #4 happening? If not, > what do you see happening? At this point, I'm wondering if the best outcome wouldn't be 6) Distros die. I'm almost not joking. > > LTS distros do update Firefox

Re: The convention to pass a parameter when ownership transfer is optional

2016-03-18 Thread jwwang
I am tempted to assume |t| will be an empty shell after foo(Move(t)) if I don't see the prototype foo(T&&). For |bar(already_AddRefed&&)|, it is also possible for the callsite to say |bar(r.forget())| without forcing the caller to handle conditional ownership transfer which won't be caught unti

An analysis of content process memory overhead

2016-03-18 Thread Nicholas Nethercote
Greetings, erahm recently wrote a nice blog post with measurements showing the overhead of enabling multiple content processes: http://www.erahm.org/2016/02/11/memory-usage-of-firefox-with-e10s-enabled/ The overhead is high -- 8 content processes *doubles* our physical memory usage -- which limi

Introducing MozGTestBench - Platform micro-benchmarks

2016-03-18 Thread Benoit Girard
In bug 1256408 I've landed code to allow adding *in-tree* platform micro-benchmarks for XUL code in less than 10 lines. These are just GTest where the execution time is reported to perfherder. This makes it easy to add low level platform micro-benchmarks for testing things that Talos is not well su

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

2016-03-18 Thread Selena Deckelmann
The two outstanding bugs are closed! We have one bug remaining that we are tracking related to metrics. I've consulted the owners of that issue and they've agreed that it is ok if that work lands shortly after we switch to Tier 1 for Linux Debug builds. We're now planning to switch TC builds to T

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-18 Thread yuhongbao_386
On Saturday, March 12, 2016 at 8:59:20 AM UTC-8, Bobby Holley wrote: > On Fri, Mar 11, 2016 at 4:28 PM, Terrence Cole wrote: > > > We've had this conversation several times in the last few years and I think > > I've finally figured out why it has always felt subtly wrong. > > > > Our share of use

Re: Intent to switch to Visual Studio 2015

2016-03-18 Thread Ehsan Akhgari
On 2016-03-18 6:43 PM, Yuhong Bao wrote: > >> On 2016-03-17 8:35 PM, Yuhong Bao wrote: On Thu, Mar 17, 2016 at 3:30 PM, mailto:yuhongbao_...@hotmail.com>> wrote: What about the depreciation of XP SP2? Results from bug 1124017 say XP SP2 still works on binaries built with >

Re: Intent to switch to Visual Studio 2015

2016-03-18 Thread Ehsan Akhgari
On 2016-03-17 8:35 PM, Yuhong Bao wrote: >> On Thu, Mar 17, 2016 at 3:30 PM, >> mailto:yuhongbao_...@hotmail.com>> wrote: >> What about the depreciation of XP SP2? >> >> Results from bug 1124017 say XP SP2 still works on binaries built with >> VS2015u1. This may not always hold true. So we will

Re: Linux distro readiness for Rust in Gecko

2016-03-18 Thread aturon
> On Fri, Mar 18, 2016 at 1:59 AM, wrote: > > In particular, as > > noted in this thread, you can't bootstrap off of either the current > > version of Rust or the previous. This is actually a problem that could > > be fixed in about one release cycle. > > Nice! I didn't realize it's that close t