WTF HashSet: Implement move semantics for values.

WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139, 582349
Committed: https://crrev.com/01875a5b228e8d84bc92db4b634df054efcf9216
Cr-Commit-Position: refs/heads/master@{#381403}

[Yuta Kitamura, 2016-03-14 10:47:24]

The CQ bit was checked by yutak@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-14 10:47:31]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1798913002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1798913002/1

[Yuta Kitamura, 2016-03-14 10:47:50]

Description was changed from

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

to

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

[Yuta Kitamura, 2016-03-14 10:47:50]

yutak@chromium.org changed reviewers:
+ haraken@chromium.org, mikhail.pozdnyakov@intel.com, tzik@chromium.org

[Yuta Kitamura, 2016-03-14 10:47:50]

yutak@chromium.org changed required reviewers:
+ haraken@chromium.org, tzik@chromium.org

[Yuta Kitamura, 2016-03-14 10:47:58]

PTAL

[commit-bot: I haz the power, 2016-03-14 12:01:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-14 12:01:40]

Dry run: This issue passed the CQ dry run.

[Yuta Kitamura, 2016-03-15 01:41:52]

Description was changed from

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

to

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

[tzik, 2016-03-15 07:25:06]

lgtm

[haraken, 2016-03-15 12:34:59]

LGTM

[Yuta Kitamura, 2016-03-16 00:32:16]

The CQ bit was checked by yutak@chromium.org

[commit-bot: I haz the power, 2016-03-16 00:32:32]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1798913002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1798913002/1

[commit-bot: I haz the power, 2016-03-16 00:34:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-16 00:34:38]

Try jobs failed on following builders:
  ios_dbg_simulator_gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_gn...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[Yuta Kitamura, 2016-03-16 01:26:26]

The CQ bit was checked by yutak@chromium.org

[Yuta Kitamura, 2016-03-16 01:26:27]

The patchset sent to the CQ was uploaded after l-g-t-m from
haraken@chromium.org, tzik@chromium.org
Link to the patchset: https://codereview.chromium.org/1798913002/#ps20001
(title: "Rebase.")

[commit-bot: I haz the power, 2016-03-16 01:26:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1798913002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1798913002/20001

[commit-bot: I haz the power, 2016-03-16 01:36:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-16 01:36:12]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Yuta Kitamura, 2016-03-16 04:18:18]

The CQ bit was checked by yutak@chromium.org

[commit-bot: I haz the power, 2016-03-16 04:18:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1798913002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1798913002/20001

[commit-bot: I haz the power, 2016-03-16 05:30:21]

Description was changed from

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

to

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

[commit-bot: I haz the power, 2016-03-16 05:30:22]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-16 05:32:19]

Description was changed from

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349
==========

to

==========
WTF HashSet: Implement move semantics for values.

This is a follow-up of the following patch where move semantics for
HashMap values were implemented:
https://codereview.chromium.org/1764973002/

This patch basically does the same thing. At this time, we don't have to
use the "Extra" part of hash table translators, since HashSet saves only
the keys.

The overload of add<Translator>(...) is renamed to addWithTranslator,
because (1) the function signatures of normal add() and translator add()
are pretty confusing, and (2) add<Translator>() version is rarely used.
I left addWithTranslator without move semantics, as I was not sure if
we should do that.

StringHash needs some modification to resolve overload ambiguities arose
from string literals.

BUG=567139,582349

Committed: https://crrev.com/01875a5b228e8d84bc92db4b634df054efcf9216
Cr-Commit-Position: refs/heads/master@{#381403}
==========

[commit-bot: I haz the power, 2016-03-16 05:32:20]

Patchset 2 (id:??) landed as
https://crrev.com/01875a5b228e8d84bc92db4b634df054efcf9216
Cr-Commit-Position: refs/heads/master@{#381403}