buddy_alloc VS GitExtensions

If you need a sub-allocator with predictable performance feel free to give it a try. The code is here and it is licensed under the 0BSD license, making it as lax and as close to public domain as possible. Comments, issues and PRs are always welcomed and appreciated. Thanks!

I maintain a project that's not technically MISRA compliant (due to being a memory allocator and MISRA disallowing the very idea) and I keep it at 100% test coverage with support for multiple compilers and operating systems. Over time I had a few users reporting back - since it's working for them I count that as success. Is it wildly popular ? Of course not, but it doesn't have to be.

You are right about the tests - they are written with 64-bit in mind. I ought to rework them to switch sizes based on arch but that will take a weekend. I've filed https://github.com/spaskalev/buddy_alloc/issues/19 to track this.

I also maintain a application-based malloc (that doesn't do obtaining and releasing memory through the OS, just managing sub-diving a larger memory block into smaller requests) at https://github.com/spaskalev/buddy_alloc - feel free to ping me with any questions about it.

I'm the author of https://github.com/spaskalev/buddy_alloc - a custom memory allocator for C (modern C11, works with C++ as well) designed for predictable and repeatable performance. It is suitable for use in embedded, games and any other system with soft or hard real-time demands. It has 100% line and branch test coverage and uses a fixed amount of space on the call stack when called. Recently the project had its first external contribution as well. Cheers!

I made a memory allocator that turned out rather neat - https://github.com/spaskalev/buddy_alloc

I agree that git is almost asking you to juggle commits.

My preference is to use temporary branches and cherry-picking instead of stashing; I mostly use a gui* to work with git so it is easy to select the two or three commits to cherry-picking or see visually if an interactive rebase would work.

* https://gitextensions.github.io/

I use Git Extensions myself as I find the git interface very straight forward, however they still have this fucking insane and frustrating issue: In the mergetool "Theirs" and "Mine" are swapped

Git Extensions is a more-intuitive way to manage your Git repositories in Windows. Its standalone interface serves as an effective, CLI-free means to control Git. Preferred by namtab00, because "SourceTree hides and shortcuts too much git functionality."

I presume this is where one goes to make a feature request? https://github.com/gitextensions/gitextensions/issues

If you're on Windows, I'd start with installing official Git. It comes with a Git Bash CLI and what not. There are also third party apps like GitExtensions and TortoiseGit if you want more UI/shell integration.

Everyone's going to downvote this, but I prefer the GUI over the command-line. I use http://gitextensions.github.io/

https://github.com/gitextensions/gitextensions/releases/tag/v2.51.05 - nice little ui for working with git. unfortunately, v2.51.05 is the last version that I can confirm works under mono (it was the last 2.x version and they completely rewrote the code from scratch in the 3.x series. My understanding was that it lost Linux compatibility at that point).