could EventReader add fn 'is_not_empty_clear()' ?

[alexniver]

        if !events.is_empty {
		events.clear();
		// Process the fact that one or more event was received
	}

this code used a lot, and new bevy coder always forget add events.clear().

maybe is_not_empty_clear is needed?

[DJMcNab]

The previous discussion of this question happened in #4693

I believe that even if such a method is added, the pit of failure of using 'normal' is_empty would still be there - if users haven't read the is_empty docs, they wouldn't know they need to use is_not_empty_clear , just as they don't know they need to use clear now.

I think the most feasible fix is the one I suggested in #4693 (comment). Basically, we should recognise that leaving an uncleared EventReader is always a logic error, so warn or panic if that occurs.

[alexniver]

oh, I like the panic idea. at least know something went wrong.

[tim-blackbird]

This would be nice as a debug assertion 👍