gecko-dev/netwerk/base/nsURIHashKey.h

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

65 строки
1.8 KiB
C
Исходник Обычный вид История

/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
2012-05-21 15:12:37 +04:00
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
#ifndef nsURIHashKey_h__
#define nsURIHashKey_h__
#include "PLDHashTable.h"
#include "nsCOMPtr.h"
#include "nsIURI.h"
#include "nsHashKeys.h"
Bug 1415980 - make hash keys movable and not copyable; r=erahm Everything that goes in a PLDHashtable (and its derivatives, like nsTHashtable) needs to inherit from PLDHashEntryHdr. But through a lack of enforcement, copy constructors for these derived classes didn't explicitly invoke the copy constructor for PLDHashEntryHdr (and the compiler didn't invoke the copy constructor for us). Instead, PLDHashTable explicitly copied around the bits that the copy constructor would have. The current setup has two problems: 1) Derived classes should be using move construction, not copy construction, since anything that's shuffling hash table keys/entries around will be using move construction. 2) Derived classes should take responsibility for transferring bits of superclass state around, and not rely on something else to handle that. The second point is not a huge problem for PLDHashTable (PLDHashTable only has to copy PLDHashEntryHdr's bits in a single place), but future hash table implementations that might move entries around more aggressively would have to insert compensation code all over the place. Additionally, if moving entries is implemented via memcpy (which is quite common), PLDHashTable copying around bits *again* is inefficient. Let's fix all these problems in one go, by: 1) Explicitly declaring the set of constructors that PLDHashEntryHdr implements (and does not implement). In particular, the copy constructor is deleted, so any derived classes that attempt to make themselves copyable will be detected at compile time: the compiler will complain that the superclass type is not copyable. This change on its own will result in many compiler errors, so... 2) Change any derived classes to implement move constructors instead of copy constructors. Note that some of these move constructors are, strictly speaking, unnecessary, since the relevant classes are moved via memcpy in nsTHashtable and its derivatives.
2018-09-20 18:20:36 +03:00
#include "mozilla/Move.h"
#include "mozilla/Unused.h"
/**
* Hashtable key class to use with nsTHashtable/nsBaseHashtable
*/
class nsURIHashKey : public PLDHashEntryHdr {
public:
typedef nsIURI* KeyType;
typedef const nsIURI* KeyTypePointer;
explicit nsURIHashKey(const nsIURI* aKey) : mKey(const_cast<nsIURI*>(aKey)) {
MOZ_COUNT_CTOR(nsURIHashKey);
}
Bug 1415980 - make hash keys movable and not copyable; r=erahm Everything that goes in a PLDHashtable (and its derivatives, like nsTHashtable) needs to inherit from PLDHashEntryHdr. But through a lack of enforcement, copy constructors for these derived classes didn't explicitly invoke the copy constructor for PLDHashEntryHdr (and the compiler didn't invoke the copy constructor for us). Instead, PLDHashTable explicitly copied around the bits that the copy constructor would have. The current setup has two problems: 1) Derived classes should be using move construction, not copy construction, since anything that's shuffling hash table keys/entries around will be using move construction. 2) Derived classes should take responsibility for transferring bits of superclass state around, and not rely on something else to handle that. The second point is not a huge problem for PLDHashTable (PLDHashTable only has to copy PLDHashEntryHdr's bits in a single place), but future hash table implementations that might move entries around more aggressively would have to insert compensation code all over the place. Additionally, if moving entries is implemented via memcpy (which is quite common), PLDHashTable copying around bits *again* is inefficient. Let's fix all these problems in one go, by: 1) Explicitly declaring the set of constructors that PLDHashEntryHdr implements (and does not implement). In particular, the copy constructor is deleted, so any derived classes that attempt to make themselves copyable will be detected at compile time: the compiler will complain that the superclass type is not copyable. This change on its own will result in many compiler errors, so... 2) Change any derived classes to implement move constructors instead of copy constructors. Note that some of these move constructors are, strictly speaking, unnecessary, since the relevant classes are moved via memcpy in nsTHashtable and its derivatives.
2018-09-20 18:20:36 +03:00
nsURIHashKey(nsURIHashKey&& toMove)
: PLDHashEntryHdr(std::move(toMove)), mKey(std::move(toMove.mKey)) {
MOZ_COUNT_CTOR(nsURIHashKey);
}
~nsURIHashKey() { MOZ_COUNT_DTOR(nsURIHashKey); }
nsIURI* GetKey() const { return mKey; }
bool KeyEquals(const nsIURI* aKey) const {
bool eq;
if (!mKey) {
return !aKey;
}
if (NS_SUCCEEDED(mKey->Equals(const_cast<nsIURI*>(aKey), &eq))) {
return eq;
}
return false;
}
static const nsIURI* KeyToPointer(nsIURI* aKey) { return aKey; }
static PLDHashNumber HashKey(const nsIURI* aKey) {
if (!aKey) {
// If the key is null, return hash for empty string.
return mozilla::HashString(EmptyCString());
}
nsAutoCString spec;
// If GetSpec() fails, ignoring the failure and proceeding with an
// empty |spec| seems like the best thing to do.
mozilla::Unused << const_cast<nsIURI*>(aKey)->GetSpec(spec);
return mozilla::HashString(spec);
}
enum { ALLOW_MEMMOVE = true };
protected:
nsCOMPtr<nsIURI> mKey;
};
#endif // nsURIHashKey_h__