introduce frictions that make it harder for an attacker to exercise voting power even once they have acquired tokens.

Other circumstances,18 combined with the increase of numbers, have produced an augmentation of revenue arising from consumption in a ratio far beyond that of population alone: and tho the changes in foreign relations, now taking place so desireably for the whole world, may for a season affect this branch of revenue, yet weighing all probabilities of expence, as well as of income, there is reasonable ground of confidence that we may now safely dispense with all the internal taxes, comprehending excises,19 stamps, auctions, licenses, carriages and refined sugars: to which the postage on newspapers may be added to facilitate the progress of information: and that the remaining sources of revenue will be sufficient to provide for the support of government, to pay the interest of the public debts, and to discharge the principals in20 shorter periods than the laws, or the general expectation had contemplated. war indeed21 and untoward events may change this prospect of things, and call for expences which the impost could not meet. but sound principles will not justify our taxing the industry of our fellow citizens to accumulate treasure for wars to happen we know not when, and which might not perhaps happen but from the temptations offered by that treasure.

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

However, IMO, having the conditional in the detach function is necessary, because there are other manifestations of this error. For example, if the DOM element in a component is removed from software outside of svelte, detach will have the same error.

IMO, the conditional needs to be added to detach to fix all manifestations of this error.