Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use either num_bytes or size_in_bytes consistently for allocation functions #690

Open
eyalroz opened this issue Oct 20, 2024 · 0 comments
Open

Use either num_bytes or size_in_bytes consistently for allocation functions #690

eyalroz opened this issue Oct 20, 2024 · 0 comments
Assignees
@eyalroz
Labels
task

Comments

@eyalroz
Copy link
Owner

eyalroz commented Oct 20, 2024

At the moment, many of our allocation-related functions take a size_in_bytes parameter, and others take num_bytes. We should choose one of these and make it uniform.
@eyalroz eyalroz added the task label Oct 20, 2024
@eyalroz eyalroz self-assigned this Oct 20, 2024
eyalroz added a commit that referenced this issue Oct 21, 2024
@eyalroz
Regards #690: We've extracted the free() calls out of the async sub…
153eb76 
…-namespace + some comment tweaks and redundancy removals
eyalroz added a commit that referenced this issue Oct 26, 2024
@eyalroz
Regards #690: We've extracted the free() calls out of the async sub…
13e4457 
…-namespace + some comment tweaks and redundancy removals
eyalroz added a commit that referenced this issue Oct 26, 2024
@eyalroz
Regards #690: We've extracted the free() calls out of the async sub…
74db33d 
…-namespace + some comment tweaks and redundancy removals
eyalroz added a commit that referenced this issue Oct 28, 2024
@eyalroz
Regards #690: We've extracted the free() calls out of the async sub…
b8dcd9b 
…-namespace + some comment tweaks and redundancy removals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eyalroz eyalroz

Labels
task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyalroz