Adding section for memory allocators and adding a first tutorial for it

[AlejandroFNadal]

Main programming language

C

Tutorial title

Malloc is not magic -- Implementing my own memory allocator

Tutorial URL

https://medium.com/p/e0354e914402

Category

• 3D Renderer
• Augmented Reality
• BitTorrent Client
• Blockchain / Cryptocurrency
• Bot
• Command-Line Tool
• Database
• Docker
• Emulator / Virtual Machine
• Front-end Framework / Library
• Game
• Git
• Memory Allocator
• Network Stack
• Neural Network
• Operating System
• Physics Engine
• Programming Language
• Regex Engine
• Search Engine
• Shell
• Template Engine
• Visual Recognition System
• Voxel Engine
• Web Search Engine
• Web Server
• Uncategorized

Notes:

Making memory allocators is great for learning to deal with memory management and understanding how things work under the hood. In this tutorial, a memory allocator is build from scratch in C, with automated testing included.

Disclaimer: this tutorial was made by me. I was inspired by the lack of a memory allocator tutorial here on this repo, and I was hoping it can be part of it. It is really detailed and it should be a fine addition to this repository. I hope you can give it a look :)

Summary by CodeRabbit

• Documentation
  • Added a new tutorial link for building your own memory allocator in C to the README under the tutorials section.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new subsection called "Build your own Memory Allocator" has been added to the README file within the tutorials section. This subsection introduces a resource link to a tutorial on implementing a memory allocator in C, positioned between the "Build your own Git" and "Build your own Network Stack" sections. No changes were made to any code files or public interfaces.

Changes

File(s)	Change Summary
README.md	Added a "Build your own Memory Allocator" subsection with a resource link to a C memory allocator tutorial.

Poem

In README fields where knowledge grows,
A new allocator link now shows.
From malloc’s magic, secrets spill—
Learn to craft your heap at will!
Between Git and Network’s call,
Memory’s mysteries now enthrall.
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[PrinceSajjadHussain]

Hi @AlejandroFNadal, thank you for contributing! The addition of a memory allocators section is a great idea. Could you ensure the tutorial aligns with the repository's structure and format? Let us know if you need help completing the remaining tasks.

[AlejandroFNadal]

Hello @PrinceSajjadHussain , thanks for your comment

Could you give me a hand by telling me where is the format incorrect? I think I have imitated the existing entries in my pull request (using bold for the language of the tutorial, a link whose name matches the title of the tutorial itself, unordered list for the item, etc).

Thanks in advance

[AlejandroFNadal]

Hello @PrinceSajjadHussain , just touching base, any pointers on how to fix my commits for the PR?

[AlejandroFNadal]

Hello @rohitpaulk , I see the person who made a comment in this PR has no more an account on github. Could you check my PR instead?

Thanks for your time and support for this amazing compilation

[PrinceSajjadHussain]

I am here

[AlejandroFNadal]

Hello @PrinceSajjadHussain sorry about my comment, I tried reaching your account and I got a 404, and that is why I assumed that your account was not available anymore.

Thanks for your PR approval. I just realized I was missing the index entry so I added it. Sorry about that inconvenience