Using mimalloc instead of malloc | Working on Windows Support

[Vizonex]

I thought of some ways to improve this program as I embark on a journey to make a windows compatible version of this project that I see having lots of potential for windows users. One of the things I am currently deciding to implement is mimalloc which is a faster version of the malloc function and is compatible with many operating systems as far as I'm aware and I wanted some input on doing so before I fork this project and start making those changes.

[nil0x42]

Hi ! Actually, duplicut's performance will be mostly unaffected by using a faster heap allocator, because it actually performs very few mallocs (two per hashmap, so 20 in total if 10 chunks are used)

So i would recommend, for windows portability, that you add windows versions for functions such as meminfo(), and wrapping calls to mmap() with a windows-compatible version, as well as fstat() & other syscall wrappers.

Indeed, if we compile for windows with mingw, it will include most of windows-compatible libc, so malloc, printf & other common functions don't need to be changed at all.

[Vizonex]

Hi ! Actually, duplicut's performance will be mostly unaffected by using a faster heap allocator, because it actually performs very few mallocs (two per hashmap, so 20 in total if 10 chunks are used)

So i would recommend, for windows portability, that you add windows versions for functions such as meminfo(), and wrapping calls to mmap() with a windows-compatible version, as well as fstat() & other syscall wrappers.

Indeed, if we compile for windows with mingw, it will include most of windows-compatible libc, so malloc, printf & other common functions don't need to be changed at all.

Good to know because I also successfully made an msvc version incase needed which I mainly did temporarily while trying to figure out how certain things work and what things might need to be implemented with other compilers, so if I do fork I should be able to take the work I did before and merge it all in. I have no exact idea on how unifying some of the external libraries I could try creating a header file which I could call compat.h where all this os compatability could be rewritten to otherwise if gets too big I'll see if making a new folder for it would be feasible.