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.

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

Make usage of _z_bytes_t / _z_slice_t more consistent #419

Closed
sashacmc opened this issue Jun 12, 2024 · 0 comments
Closed

Make usage of _z_bytes_t / _z_slice_t more consistent #419

sashacmc opened this issue Jun 12, 2024 · 0 comments
Labels
release Part of the next release

Comments

@sashacmc
Copy link
Member

Describe the release item

If variable named payload it should be _z_bytes_t (or z_owned_bytes_t, z_loaned_bytes_t in API)
If at the level of abstraction under consideration we can forget about _z_bytes_t and we can honestly consider memory as a solid piece (aka _z_slice_t), then the variable name should not be payload to avoid confusion.
There should also be no variables with the name bytes and type _z_slice_t

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Part of the next release
Projects
Status: Done
Development

No branches or pull requests

1 participant