Multiple-injection

[ilyapuchka]

Resolves #14

[AliSoftware]

registered

[AliSoftware]

Already said that in #14 but I'm really not sure this is worth adding.

I like having a library that doesn't become a huge do-it-all lib. Keeping the API simple is important to me, and adding convenience methods to do something that the user can really easily do on its own if really needed does not seem to go in that direction, but rather adds methods in the API for which the user might wonder why it's here (in the sense "that feature is so simple to do it on my own, why is there a dedicated method to do this, if there is a dedicated method does it means that this is in fact not as obvious as I think it is?" etc)

In your examples, it seems to me that using a simple map allows to achieve the exact same effect that this feature does:

enum Services: String {
  case GMail, Yahoo, Outlook
  let allValues: [Services] = [.GMail, .Yahoo, .Outlook]
}
container.register(tag: Services.GMail) { GmailService() as ThirdPartyEmailService }
container.register(tag: Services.Yahoo) { YahooService() as ThirdPartyEmailService }
container.register(tag: Services.Outlook) { OutlookService() as ThirdPartyEmailService }

let thirdPartyServices = Services.allValues.map { try! container.resolve(tag: $0) as ThirdPartyEmailService }

Then, exactly like in your example in the playground, if you realize later that you want to add a service, simply add it in the allValues property of the enum.

[ilyapuchka]

Sure, it can be done by user with ease. I'm ok with not including that feature.