mimalloc 2.1.7 & 1.8.7

[maximegmd]

• Before adding new features and new modules, please go to issues to submit the relevant feature description first.
• Write good commit messages and use the same coding conventions as the rest of the project.
• Please commit code to dev branch and we will merge into master branch in feature
• Ensure your edited codes with four spaces instead of TAB.

---

• 增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
• 编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
• 请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
• 为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。

[waruqi]

Please add only one version per pr for ci test

[SirLynix]

since a newer version than 1.8.7 is already present, the CI won't test it anyway, it only tests the last one, right?

[waruqi]

since a newer version than 1.8.7 is already present, the CI won't test it anyway, it only tests the last one, right?

right, this would require an improved test script, or commenting out the higher version first to test the lower version.

[star-hengxing]

Improve test script or make two package

mimalloc1 -> 1.x mimalloc -> 2.x

[SirLynix]

I don't think we should split packages by their version except in some cases (like openssl) maybe we could somehow extract added version in the test script, based on git diff perhaps

[star-hengxing]

add_version_branch("1.x", "2.x")
-- Test script will test 1.x and 2.x latest version

[SirLynix]

{ 
  "mimalloc 2.1.7",
  "mimalloc 1.8.7",
}

amazing!