On Nov 8, 4:11pm, Peter Stephenson wrote:
}
} It seems to me it's equally not an error to mark zstat as a builtin from
} zsh/stat if it's already loaded as a builtin from zsh/stat. It would
} only be an error if there's a conflict.
}
} That's how "autoload" works, after all: it can't check for a conflict
} (without major faff) but it does check if a function's already loaded.
I'm confused; these statements seem contradictory, so I must be missing
something. If we can't check for a conflict, how can we suppress the
error message? I.e., how do we know that zstat is already loaded as a
builtin from the same module we're now loading?