|
|
|
|
|
|
by phil-opp
2323 days ago
|
|
|
> The overflow scenario should be treated the same as the out-of-memory scenario and also return null. Good point! I'll prepare an update to fix this. > It can do better, in `dealloc` you can use `ptr` and `layout` to check if the allocation is at the end of the allocated region. If it is, `bump.next` can be reduced by `layout.size()`. This is optimal for lifo/stack style allocation patterns. You're right. I already created a PR [1] for this shortly after publishing the article, but it seems like I forgot to merge it. There should be now an additional "Fixing the Test?" section that talks about freeing the last allocation. [1]: https://github.com/phil-opp/blog_os/pull/722 |
|
|
Update in https://github.com/phil-opp/blog_os/pull/738 and https://github.com/phil-opp/blog_os/pull/739