example.swift

struct Fields {
  var userFields: Set<User.Fields>?
  var tweetFields: Set<Tweet.Fields>?
}

protocol Fetcher {
  // Is there a way to do something like this, where I can specify that the `Fields`
  // struct must contain only these member types?
  func getTweet(fields: Fields<Tweet.Fields, User.Fields>? = nil) async -> Tweet
  func getUser(fields: Fields<User.Fields>? = nil) async -> User
}

@fourplusone thanks for the reply and suggestion! Separate fields parameters is what I originally had in the function design but some functions could accept up to 5 distinct field types so function calls could get pretty unwieldy.

This helped me think about another way to express it though. Since the function calls with multiple field types usually follow a pattern (a single primary field type such as Tweet.Fields, and then one or more secondary field types for expansions like Users, Polls, Media, etc), I can probably make the secondary field types associated values on the expansions enum. This has two advantages: removes the need for the generic Fields struct to act as a container, and ensures only field types that are allowed with the expected expansions.

Example function call after this change:

let userFields: [User.Fields] = [.pinnedTweetId, .profileImageURL]
let expansions: [User.Expansions] = [.pinnedTweetId(tweetFields: [.createdAt])]
getUser(userId, userFields: userFields, expansions: expansions)