Theoretically yes, in this usecase it wouldn't be a gain. This is for a framework that accepts procs from a user, so you do not control what kind of proc gets passed in there.
An effect is basically not being validated there, or rather there's no validation beyond the user applying said effect-pragma to their proc which they may do blindly. At that point the effects system is nothing more than an annoyance to the user, so you may as well leave it out. For larger applications where you control multiple sides of the equation (or if we had some standard effect-types in the nim-ecosystem for e.g. this kind of scenario) I think this is still valuable. Just not in this scenario.
