CS371p

Write a program, ideally with a partner, to solve Ed Lessons' Allocator [g++ 14.1.1, C++20 standard].
You may not use new, delete, malloc() or free(). You may use the STL.

fork the public code repo (https://gitlab.com/gpdowning/cs371p-allocator/) to become your private code repo (https://gitlab.com/GitLabID/cs371p-allocator/)
enable issues here: Settings -> General -> Visibility, project features, permissions -> Issues
create the following issue labels here: Issues -> New Issue -> Labels -> Manage project labels (labels are case sensitive):
- build (Titanium yellow)
- code (Dark violet)
- documentation (Gray)
- tests (Dark coral)
import the issues: Issues -> Import issues -> Import CSV
close all provided issues
add and close new issues as you debug and develop your solution
provide your GitLab URL on the Canvas assignment

Assets	Location
Correctness 5 tests at least 3 tests to be eligible to resubmit	Ed Lessons `Allocator.cpp` (combine `Allocator.hpp` and `run_Allocator.cpp`)
Build Files .gitignore .gitlab-ci.yml Makefile README.md	GitLab
Issues add at least 5 more issues	GitLab
Unit Tests between 10 and 20 tests run gcov run Valgrind	test_Allocator.cpp
Acceptance Tests between 20 and 30 tests, between 200 and 300 lines, total run checktestdata do not run gcov do not run Valgrind	run_Allocator.ctd.txt run_Allocator.cpp https://gitlab.com/gpdowning/cs371p-allocator-tests/gpdowning-Allocator.in.txt via merge request https://gitlab.com/gpdowning/cs371p-allocator-tests/gpdowning-Allocator.out.txt via merge request
Continuous Integration	GitLab Pipelines
Code assertions run astyle run cppcheck	Allocator.hpp
Documentation create inline comments if you need to explain the why of a particular implementation run doxygen (Allocator.hpp only) git log	Allocator.html Allocator.log.txt