On 5/21/2016 5:52 PM, Era Scarecrow wrote:
I'm going to try for a lookback and scan which uses quite a bit of memory. On the other hand you can reuse the memory over and over again, so that isn't an issue. Although it will take up a Meg in memory. Also written entirely in D, so...I think I'll go with a similar setup you have for the encoding (3 bytes). Should be nearly identical in output.
Just a note: large lookup tables can have cold cache performance problems.
