[FEATURE REQ] Page<T> and Response<T> should implement or inherit from a common ancestor

Library or service name. What library or service is this request related to? Azure.Core

Is your feature request related to a problem? Please describe. Currently, Page<T> is a basic class that has no inheritance or implementation chain. However, it is in fact very similar to a Response<T> - it is a page of results that come down through a Response. Accordingly, both types have the GetRawResponse() method. Therefore, there should be some common ancestor between the two so that methods can accept an argument that matches either of these types. Currently, there is no clean way of achieving this behavior.

[pakrym]

Don’t think the use case is common enough to motivate adding this feature.

[KrzysztofCwalina]

I’m proposing that Page<T> and Response<T> implement/inherit a common ancestor, and not that Page<T> inherit from Response<T>.

Ah, sorry, I missed that.