Ah, I think I have an interesting use case here: declaring a partial borrow without actually using the member. See this MR (though in particular this commit). Here, the highlighted commit, instead of making a new type, may have been able to utilize partial borrowing to declare that using the writer is a conceptual &mut borrow of data even though there is no method that uses both syntactically. The point is that even though data is not mentioned, it must be considered borrowed in order to avoid a deadlock because the receiving end of writer needs a write lock on the RwLock<data::Data> to actually consume items from the channel.
To me, this means that there must be a way to explicitly list members that are considered borrowed even if there is support for implicit computation because there may be safety considerations in how members are grouped into types (not that this example is one of Rust safety/soundness guarantees given that the deadlock behavior is Rust-safe, but someone can probably craft such an example).