On Thu, Jan 7, 2010 at 8:00 PM, Michael Nordman <[email protected]> wrote:
> Where as It looks like GURL::EmptyGURL() may be a tad less costly than > GURL(). > Not if you ever need to initialize another GURL with it (since the compiler can't collapse the copy). Which is true much of the time that EmptyGURL() can be replaced by GURL(). And the code clarity reasons still stand. Please don't do this in the name of hoping you'll save an instruction somewhere, it's much like premature optimization. PK
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
