Every submission runs through real compilers, sanitizers and a quality grader. You don't just see "accepted" — you see how good your code actually is.
Allocate a pool up front and hand out unique_ptr handles that return to the pool on destruction. No heap churn, no leaks.
template<class T>
unique_ptr<T, Ret> acquire() {
auto i = free_.back(); free_.pop_back();
return { &slots_[i], Ret{this, i} };
}
// return slot to the pool on destroy
void operator()(T* p) { free_.push_back(p - slots_); }GCC & Clang with -Wall -Wextra. Warnings count.
Unit tests against your implementation, edge cases included.
ASan + UBSan catch leaks, memory errors and undefined behaviour.
AST analysis scores RAII, ownership and idioms.