Added sample of Event Bus with superpowers

[oskardudycz]

List of superpowers:

• filtering,
• transformation 1:1 and 1:N events into events,
• no requirement for a marker interface for events,
• no requirement for marker interfaces for handlers: supports pure function with wrappers,
• but if you really want, you can have interfaces,
• supports IoC, but also allow manual composition,
• can be plugged into MediatR if you want.

[kbroniek]

Consider implementing a query method as well.

[kbroniek]

Suggested change

	async ValueTask<object?> IEventHandler.Handle(object @event, CancellationToken ct)
	{
	return await Handle((TEvent)@event, ct);
	ValueTask<object?> IEventHandler.Handle(object @event, CancellationToken ct)
	{
	return Handle((TEvent)@event, ct);

[oskardudycz]

@kbroniek, thank you for the suggestion. This sample is more focused on the Events Broadcast, so publishing events to subscribers. Do you see potential in that? My intent wasn't to replace MediatR, but indeed that approach could also work for any processing 🤔 Thoughts?

[kbroniek]

OK. It will be nice to add a benchmark, but I know it will consume your time that we don't have these days.
Thought you could implement this as .net events or take advantage of source code generation. It could be fast then.
What if we add multiple handlers in the multi-threading app. Consider using ConcurrentDictionary.

[oskardudycz]

Fair points. I added an issue for that: #85. I'll tackle that in a dedicated PR, as this branch is living too long. It's about time to kill it 😉