Allocation algorithm description in readme is different from the code

[vagran]

This fragment:

This one is prety easy too, except we don't need to mess with the free list indexes at all becasue we'll allocate the new block at the end of the current free block. We do, however have to adjust the indexes in cf, c, and n.

does not correspond to the actual logic in the code. Is there any reason why it was not implemented as described in readme? If so, the readme probably should be updated.

[rhempel]

I was wondering why someone would read the comments and code so closely - super interesting that you are writing an allocator in zig based on this :-)

I will have a look at this issue and wait a little while in case you find other things to fix in the docs.

Thanks for taking the time to send feedback - I'm glad this little allocator has been around for so long and has been helpful.

[vagran]

I am actually just fixing bugs in Zig port of this nice allocator, so I had to dive deep. And I am currently done.

Bonus fix in the docs could be this:

An asterisk is rendered in Markdown as a bullet point, so it confuses a bit, should be taken in backticks.
Thanks for your work!