Skip to content

Conversation

@redbaron
Copy link
Contributor

@redbaron redbaron commented Feb 8, 2023

sendmsg can be used on connected sockets without msg_name.

@FrankReh
Copy link
Collaborator

FrankReh commented Feb 8, 2023

These changes may be a step in the right direction but they are not complete. The branch doesn't compile.

Please run cargo build and cargo test on your branch before starting a PR. Also cargo fmt and cargo clippy. All with the most recent compiler. In this case, you can make additional commits to your branch. See all those commands pass and then push up to GitHub again.

Here, even the file src/io/sendmsg_zc.rs which you changed won't compile, let along the entire library not compiling.

And while your comment about sendmsg is correct, please include a link to an online manpage from some place like arch linux so anyone reading through this can be starting with the same understanding.

Thank you.

Edit: Perhaps your point was just to highlight a shortcoming in the API but did not want to offer a solution - I've sometimes done that in other repos. Then just opening an Issue would be a better vehicle.

sendmsg can be used on connected sockets without
msg_name.
@redbaron
Copy link
Contributor Author

redbaron commented Feb 9, 2023

I am really sorry for incomplete PR, IDK how it happened. Pushed fixed version.

Copy link
Collaborator

@FrankReh FrankReh left a comment

Choose a reason for hiding this comment

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

Looking good. Just asking for some small changes, all in net/udp.rs I think.

@redbaron redbaron requested a review from FrankReh February 13, 2023 08:09
@FrankReh FrankReh merged commit e05ca59 into tokio-rs:master Feb 13, 2023
@FrankReh
Copy link
Collaborator

Thank you!

@redbaron
Copy link
Contributor Author

Thank you!

I didn't realise you'd merge it straight away, my intention was to get approval then squash all changes. sorry for many useless commits

@redbaron redbaron deleted the msghdr-noname branch February 13, 2023 15:12
@FrankReh
Copy link
Collaborator

We squash the changes for every PR in this repo. At least we mean to. There may have been some that slipped through. All the commits weren't a problem. The GitHub merge will do the squash for us if we like. I did end up pulling this branch locally to be able to look through things when there were problems. The final merge from master I didn't see needing to wait for you as it might have taken another day for the turn around. And there are a number of outstanding PRs that can get merged when another maintainer has a look so I wanted as much committed and remerged to the other PRs as quickly as possible.

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