✅ Is there a reason to still be using EventArgs and EventHandler<T> for events?
I see the usage of both aforementioned types in the msdocs for events. Even in new-ish blogs and packages, I see some people still using this approach. However, I fail to see a point to it.
Event declarations can be of any delegate, like Action<T> or Func<T, T>. And EventArgs seems utterly pointless.
So, I just want to make sure: Is this just an outdated convention? Or are there secret runtime benefits of doing events this way?
Event declarations can be of any delegate, like Action<T> or Func<T, T>. And EventArgs seems utterly pointless.
So, I just want to make sure: Is this just an outdated convention? Or are there secret runtime benefits of doing events this way?
