-
-
Notifications
You must be signed in to change notification settings - Fork 80
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.
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
Use either num_bytes or size_in_bytes consistently for allocation functions #690
Labels
Comments
eyalroz
added a commit
that referenced
this issue
Oct 21, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Oct 26, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Oct 26, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Oct 28, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Nov 15, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
…-namespace + some comment tweaks and redundancy removals
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
…-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
At the moment, many of our allocation-related functions take a
size_in_bytes
parameter, and others takenum_bytes
. We should choose one of these and make it uniform.The text was updated successfully, but these errors were encountered: