quick-lint-js VS OptSched

You were write. Fucking sleeper shill https://github.com/quick-lint/quick-lint-js/blob/master/tools/ci-analytics/github_api.go

pretty insane this issue queue...not that most open source is lucrative but putting low ball price tags on it like this is...not my style let's just say https://github.com/quick-lint/quick-lint-js/issues

My allocator is 258 SLOC.

quick-lint-js (my project) is written in C++. It:

generator: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/tools/generate-lex-unicode/index.js table: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex-unicode.cpp lookup: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex.cpp#L89-L109

use /u/strager's quick-lint, its better.

Idk if this is too complicated for what you have in mind, but https://github.com/CSUS-LLVM/OptSched (~18k LOC) is an active academic research project implementing a combinatorial instruction scheduler for LLVM. Unfortunately, the contributors (mostly undergrads and recent grads, but some graduate school too) have not had enough time to refactor it, as they've all been busy working on their respective projects. It's also a challenge to refactor things, since there's very few tests and most contributors are working with very long feature branches (months), although I've been trying to encourage some change in that area.