Talk:Hash join: Difference between revisions
Content added Content deleted
(reasons for demotion) |
(seems like a fine (draft) task to me) |
||
Line 1: | Line 1: | ||
I've downgraded to a draft task for now; we need more implementations (preferably independent ones!) so that we can be sure that a sufficient common understanding if the task exists. Once there are four language implementations, we can promote back. Also, what about language/runtime systems with built-in hash table support? –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 22:47, 30 November 2013 (UTC) |
I've downgraded to a draft task for now; we need more implementations (preferably independent ones!) so that we can be sure that a sufficient common understanding if the task exists. Once there are four language implementations, we can promote back. Also, what about language/runtime systems with built-in hash table support? –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 22:47, 30 November 2013 (UTC) |
||
:Agree on the draft status for now. And despite the, er, fireworks accompanying its creation, I suspect it'll be a good task. I don't see how the built-in-ness of hashes plays one way or the other. The task merely assumes that an appropriate hash implementation will be used, whether built-in or imported or implemented as part of the solution. --[[User:TimToady|TimToady]] ([[User talk:TimToady|talk]]) 04:05, 3 December 2013 (UTC) |
Revision as of 04:05, 3 December 2013
I've downgraded to a draft task for now; we need more implementations (preferably independent ones!) so that we can be sure that a sufficient common understanding if the task exists. Once there are four language implementations, we can promote back. Also, what about language/runtime systems with built-in hash table support? –Donal Fellows (talk) 22:47, 30 November 2013 (UTC)
- Agree on the draft status for now. And despite the, er, fireworks accompanying its creation, I suspect it'll be a good task. I don't see how the built-in-ness of hashes plays one way or the other. The task merely assumes that an appropriate hash implementation will be used, whether built-in or imported or implemented as part of the solution. --TimToady (talk) 04:05, 3 December 2013 (UTC)