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

Add recv_blocking_with_flags #2102

Merged
merged 2 commits into from
Apr 26, 2024
Merged

Add recv_blocking_with_flags #2102

merged 2 commits into from
Apr 26, 2024

Conversation

addisoncrump
Copy link
Collaborator

This adds a blocking version of recv_buf_with_flags to both the llmp receiver and client. This allows for easier creation of external LLMP clients.

@addisoncrump addisoncrump force-pushed the llmp-blocking-recv-flags branch from d115efe to d51a4af Compare April 25, 2024 10:24
/// Receive the buffer, also reading the LLMP internal message flags
#[allow(clippy::type_complexity)]
#[inline]
pub fn recv_buf_blocking_with_flags(&mut self) -> Result<(ClientId, Tag, Flags, &[u8]), Error> {
Copy link
Member

Choose a reason for hiding this comment

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

Instead of allowing type_complexity, maybe it's time for a struct?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure, let's include that change in #2068?

@addisoncrump
Copy link
Collaborator Author

Am I good to merge this?

@tokatoka tokatoka merged commit c2e0e8d into main Apr 26, 2024
100 checks passed
@tokatoka tokatoka deleted the llmp-blocking-recv-flags branch April 26, 2024 14:22
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