Why do we use client.WatchAsync<TEntity>() rather than client.Watch<TEntity>() for the entity watcher?

[slacki123]

Hi, just wondering why do we use the WatchAsync<TEntity>() instead of the Watch<TEntity>() method to watch for custom resources here
https://github.com/buehler/dotnet-operator-sdk/blob/main/src/KubeOps.Operator/Watcher/ResourceWatcher%7BTEntity%7D.cs#L139

I recently implemented some of my own watchers with the Watch() method and it works really well with simple implementation. What's the reasoning for using WatchAsync<TEntity>()? Is it because Watch<TEntity>() wasn't available when the operator was first written or is it lacking some functionality?

[buehler]

Hey @slacki123

The reason is simply that when I rewrote v8, I used async enumerables and other modern language features. There is no particular reason.