As said, while looking mildly prettier, this still renders the library completely useless in this case. I don't think there is any valid reason for us to bail out on init just because a single type is not loaded properly.

So, sure, we can merge this, but we can not claim that it fixes the reported issue.

@filmor the fix is the new null check inShouldBindEvent.

The rest is to make it easier to do bug reports: the error data will now at least contain the name of the type that we failed to process.

I see. Still don't see why makingShouldBindEvent special in that it swallows the error instead of throwing is better than just behaving like this uniformly. I'd rather have none of these functions throw, but at least it fixes the reported issue.

@filmor it does not swallow the error.

The checks on methods and fields are different. They actually check that method or field was passed, and not justnull. In case of event the event itself must exist as well (e.g. not null), but some events apparently do not have a corresponding add method for handlers:AddMethod property is nullable

BTW I was unable to reproduce it with C#.