Skip to content

Conversation

@LuAbelt
Copy link
Contributor

@LuAbelt LuAbelt commented May 1, 2025

No description provided.

@LuAbelt LuAbelt requested a review from vulder May 1, 2025 09:19
Copy link
Contributor

@vulder vulder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also fix the formatting of this PR.

PS: pls double check you pre-commit is not running in the CI.

}

inline void free_memory(void* mem){
use_memory(mem);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this. Why do you think we need this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if I had a specific intent in mind with this, other than to have both a function for allocation and freeing memory that automatically "uses" the memory. In hindsight, I don't see any realistic use cases for this at the moment to be honest.

I guess we remove it then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants