Re: Unknown performance pitfall in tables?

[cblake]

Oh, and one other number - your original code with PGO on that same input - 72 
ms. So, the double/triple table lookup/slice stuff is really all only costing 
around 72/66 =~ 9%.