C++ 模板化容器类:如何最好地支持有序和无序的项目类型?
我正在编写一个模板化的 C++ 通用容器类,它可以选择以明确定义的顺序维护其内容。 以前它使用函数指针以特定于类型的合理方式对其内容进行排序,但我尝试将其更改为使用模板化函子参数。
由于通常情况下,类的用户可能希望在不同的容器中以不同的方式保留相同类型的项目,因此容器类采用可选的模板参数,该参数允许用户选择指定自己的比较函子
template <class ItemType, class CompareFunctorType = CompareFunctor<ItemType> > class MyContainer
{
[...]
};
:不指定自定义函子类型,它默认使用以下 CompareFunctor 定义:
template <typename ItemType> class CompareFunctor
{
public:
bool IsItemLessThan(const ItemType & a, const ItemType & b) const
{
return (a<b); // will compile only for types with < operator
}
};
这对于内置类型以及定义了小于运算符的用户定义类型非常有用。 但是,我希望它也能自动适用于没有内置或显式定义的小于运算符的类型。 对于这些类型,容器内物品的顺序并不重要。
动机是我使用这个容器来容纳很多不同的类型,大多数时候,我不关心容器中类型的顺序,但在某些情况下我会关心......而且我不关心不想必须进去并向所有这些不同类型添加“虚拟”小于运算符,这样我就可以将它们与这个容器类一起使用......并且我不想必须显式指定自定义“虚拟”每次我使用表来存储没有小于运算符的项目时,都会使用 CompareFunctor 参数。
那么,有没有一种方法可以使用模板专门化(或其他东西),以便尽可能使用默认的 CompareFunctor (如上所示),但在 CompareFunctor 会导致错误的情况下,C++ 会自动回退到“虚拟” FallbackCompareFunctor 就像下面的那样? 或者也许有其他聪明的方法来解决这个困境?
template <typename ItemType> class FallbackCompareFunctor
{
public:
bool IsItemLessThan(const ItemType & a, const ItemType & b) const
{
return ((&a)<(&b)); // will compile for all types (useful for types where the ordering is not important)
}
};
I'm writing a templated C++ generic container class that can optionally maintain its contents in a well-defined order. Previously it used function pointers to order its contents in a sensible type-specific way, but I am attempting to change it to use templated functor arguments instead.
Since it's often the case that the class's user might want to keep items of the same type sorted in different ways in different containers, the container class takes an optional template argument that lets the user optionally specify his own compare-functor:
template <class ItemType, class CompareFunctorType = CompareFunctor<ItemType> > class MyContainer
{
[...]
};
If the class user doesn't specify a custom functor type, it uses the following CompareFunctor definition by default:
template <typename ItemType> class CompareFunctor
{
public:
bool IsItemLessThan(const ItemType & a, const ItemType & b) const
{
return (a<b); // will compile only for types with < operator
}
};
This works great for built-in types and also user-defined types where a less-than operator has been defined. However, I'd like it to also automatically work for types where there is no built-in or explicitly defined less-than operator. For those types, the ordering of the items within the container is not important.
The motivation is that I use this container to hold a lot of different types, and most of the time, I don't care about the order of the types in the container, but in some cases I do... and I don't want to have to go in and add "dummy" less-than operators to all of these different types just so I can use them with this container class... and I don't want to have to explicitly specify a custom "dummy" CompareFunctor argument every time I use the table to store items that don't have a less-than operator.
So, is there a way I can use template specialization (or something) so that the default CompareFunctor (shown above) is used whenever possible, but in cases where that CompareFunctor would cause an error, C++ would automatically fall back to a "dummy" FallbackCompareFunctor like the one below? Or perhaps some other clever way to handle this dilemna?
template <typename ItemType> class FallbackCompareFunctor
{
public:
bool IsItemLessThan(const ItemType & a, const ItemType & b) const
{
return ((&a)<(&b)); // will compile for all types (useful for types where the ordering is not important)
}
};
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
对于默认的未排序情况,请使用 Null Comparison 函子,该函子对所有情况都返回 false。
然后,您可以使用 std::less() 函子将模板专门化为排序容器。
For your default unsorted case, use a Null Comparison functor that just returns false for all cases.
You can then specialise your template to a sorted container using the std::less() functor.
在根据尤金的回答进行一些谷歌搜索时,我发现了这篇文章:
http ://www.martinecker.com/wiki/index.php?title=Detecting_the_Existence_of_Operators_at_Compile-Time
也许我可以调整那里提供的代码......
While doing some Google searches based on Eugene's answer, I found this article:
http://www.martinecker.com/wiki/index.php?title=Detecting_the_Existence_of_Operators_at_Compile-Time
Perhaps I can adapt the code presented there...
如果有人感兴趣,我可以结合使用上述技术想出一种方法来做我想做的事情。 我的概念验证代码(带有单元测试)如下所示。
In case anyone is interested, I was able to come up with a way to do what I wanted, using a combination of the techniques described above. My proof-of-concept code (with unit test) is shown below.
boost::enable_if 可以打开模板特化并基于一些编译时评估。
如果您可以创建一个在您检查的类型没有小于运算符的情况下在编译时计算结果为 false 的构造,那么您可以使用它来启用 CompareFunctor::IsItemLessThan 的回退专门化。
当然,您还需要 some_condition 来以某种方式检查运算符 lessthan...我想看看 boost::type_traits 和 MPL 代码——它们做了类似的事情。
boost::enable_if can turn template specializations on and off based on some compile time evaluation.
If you can create a construct that would evaluate to false at compile time if the type you are checking doesn't have lessthan operator, then you can use that to enable fallback specialization for CompareFunctor::IsItemLessThan.
Of course you also need some_condition to check for operator lessthan somehow... Look at boost::type_traits and MPL code I guess -- they do similar stuff.