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
Change retransmittable to Ack-eliciting #1942
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We considered ack-eliciting before. I'm still not a big fan of it, but I can't say anything against it other than retransmittable reads a bit better.
Yeah - retransmittable doesn’t mean it has to, only that it can be. |
I'm not set on this being what we go with, but I think it reads reasonably well and I'm really unhappy with retransmittable, since I think it's just confusing. If there's another alternative you'd like to see me create a PR for, feel free to suggest it. |
Does the English language have a suffix that means that something must be done ("ack |
Based on this list of English suffixes, I propose that we use ackent instead of ack-eliciting. The suffix ENT means "one who performs/causes." Thus, instead of
we will have
|
resilient
unforgettable
unmissable
robust
stateful
|
@mikkelfj, my suggestion was in earnest. |
Mine was only half in jest. I kind of like resilient. |
Ack-eliciting is slightly shorter than retransmittable and seems as accurate as anything we have.
Fixes #1595