On Sat, Jun 14, 2025 at 08:59:39AM -0400, Mark Johnston wrote: M> If your suggestion is implemented, then it would be sensible to use a M> different name to avoid collisions, maybe SET_EXTERROR() or just M> EXTERROR().
I'd vote for EXTERROR(). But now with the function existing, why would we recommend to use the macro instead of the function at all? IMHO, the function shall be the right use and that will make any macro collisions with ZFS or whatever void. -- Gleb Smirnoff
