动态哈希->类标签
我有:
const unsigned int hash_1 = 0xaf019b0c;
const unsigned int hash_2 = 0xf864e55c;
const unsigned int hash_3 = 0xfaea8ed5;
哈希值来自自动生成的标头。这些哈希值间接与标签 1、2、3 关联。标签通过简单的编译时生成的 id 与类关联。这样我就可以 GetTag
并获取 Class1 的 int 标签。
我的目标是简化哈希->标签关联。最好是编译时生成且访问时间为 O(1)。在这种情况下,内存不是问题。我无法使用任何第三方软件。
我尝试了以下方法:
template<uint32 t> size_t GetTagByHash() { return 0; }
使用特定的实现,例如:
template<> size_t GetTagByHash<hash_1>() { return GetTag<Class1>(); }
但是这种实现很难使用,因为如果我有一个局部变量 uint32 my_hash;
,编译器无法确定它在编译中具有什么值-time,则编译器无法解析要调用的 GetTagByHash()
的正确实现。
I have:
const unsigned int hash_1 = 0xaf019b0c;
const unsigned int hash_2 = 0xf864e55c;
const unsigned int hash_3 = 0xfaea8ed5;
Hashes come from an automatically generated header. These hashes are indirectly associated with tags 1, 2, 3. The tags are associated with classes through a simple compile-time generated id. That way I can GetTag<Class1>()
and get my int-tag for Class1.
My goal is to simplify the hash->tag association. Preferably this should be compile-time generated and O(1) access time. Memory in this case is not an issue. I can not use any third-party software.
I have tried the following:
template<uint32 t> size_t GetTagByHash() { return 0; }
with specific implementations like:
template<> size_t GetTagByHash<hash_1>() { return GetTag<Class1>(); }
but that kind of implementation is difficult to use since if I have a local variable uint32 my_hash;
that the compiler can't determine what value it has in compile-time then the compiler is unable to resolve the correct implementation of GetTagByHash()
to call.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
据我了解,您的问题是如何使用运行时值和编译时值进行查找。
你确实有两个问题。首先,您想使用什么算法来进行查找,其次,您如何告诉 C++ 来实现它?
使用哪种算法是一个不太明显的问题;您有一个有效随机数的列表,并且您想要在该列表中查找某些内容并返回关联的标签。也许您想要某种哈希表,但首先,我将展示一些更简单的示例 - 对于少量哈希可能更好:一个简单的 O(N) 查找,用伪代码表示:
现在,您如何判断C++ 能做到这一点吗?您必须创建所有哈希标签的列表以及执行此操作的说明。这是一个简单的方法:
等等。然后,最后,你可以
写出所有这些相同的定义,虽然很痛苦,所以最好让 C++ 来做这件事——而且,要做到这一点,你需要以这样的方式定义哈希值:被迭代。让我们这样做:
然后,您像以前一样使用它。
现在,让我们回到第一个问题——您实际上想使用什么算法来进行查找?这种迭代 O(N) 查找的优点是它易于编程,并且不需要在运行时对任何数据结构进行任何初始化——您只需调用它即可。然而,正如所指出的,它的复杂度是 O(N)。另一种选择是使用 std::map 对象;您可以使用类似的递归定义在运行时初始化它,然后使用它。这可能看起来像这样:
就个人而言,我可能会将其与您的
GetTagByHash<>
想法结合起来,并为 Hash_loop 提供我所描述的“运行时计算结果”函数,以及“编译时计算结果”函数采用模板参数而不是函数参数。但是,一般来说,这是进行运行时查找的基本思想 - 将要查找的值放入一组模板化类中,您可以在编译时递归地迭代这些类,然后使用该递归迭代来定义查找函数或初始化可用于执行查找的运行时结构。As I understand it, your problem is how to do this lookup with run-time values as well as compile-time ones.
You've really got two questions. First, what algorithm do you want to use to do the lookup, and second, how do you tell C++ to implement that?
The algorithm to use is somewhat of a non-obvious question; you've got a list of effectively-random numbers, and you want to look up something in that list and return an associated tag. Probably you want some sort of hashtable, but to start with, I'll show some examples with something simpler -- and likely better for small numbers of hashes: A simple O(N) lookup, in pseudocode:
Now, how do you tell C++ to do this? You've got to create a list of all your hash tags, and instructions for doing that. Here's a simple way:
And so forth. Then, at the end, you can have
Writing out all those identical definitions is a pain, though, so it's best to let C++ do that -- and, to do that, you need to define the hashes in such a way that they can be iterated over. Let's do that:
Then, you use this as before.
Now, let's return to that first question -- what algorithm do you actually want to use to do the lookup? The advantage of this iterative O(N) lookup is that it's easy to program, and it doesn't require any initialization of any data structures at run-time -- you can just call it. However, as noted, it's O(N). An alternate choice is to use a
std::map
object; you can use a similar recursive definition to initialize it at runtime, and then use it. That might look something like this:Personally, I would probably combine this with your
GetTagByHash<>
idea, and give the Hash_loop a "runtime-computed result" function as I described, as well as a "compile-time-computed result" function that takes a template argument rather than a function argument. But, in general, that's the basic idea for doing runtime lookup -- you put the values you want to look up into a set of templated classes that you can recursively iterate over at compile time, and then you use that recursive iteration to either define a lookup function or initialize a runtime structure that you can use for doing the lookup.