Would it be correct to rephrase it along the lines of "seeks forward from the current position by the specified number of bytes, and then if that's in a hole, seeks forward until it reaches data" or so?

Yes, I think this would be much clearer. My only concern is if it's preferable that the wording of the documentation remain consistent across SeekFrom variants?

How about, "Sets the offset to the current position plus the specified number of bytes, plus the distance to the next byte which is not in a hole."?

The change here looks good to me.

That said, it looks like this change needs a semver bump, because users using std::io::SeekFrom will need to switch to rustix's. I'm hoping to avoid doing a semver bump in rustix for a while. If you'd like this feature to show up in a release sooner, what would you think of renaming seek to seek_ext or something, and re-introducing the old seek that takes a std::io::SeekFrom, so that it's semver-compatible?

I'm not pressed for this feature currently, I just was interested in its absence in the API. My use for it is in an experimental PR which will not be merged soon, if ever. This should probably be placed in some kind of 0.37 milestone or something.

Sounds good. I've now added a 0.37 label and labelled this PR with it.

#487 landed, which will need a semver bump, so let's land this too.