glob should not lstat with --no-dir

Bug report form

• I have done a basic search of the issue tracker to find any existing issues that are similar.
• I have checked that my version is at least the latest stable release available via my installation method.

Describe the bug

In the beginning, unix had stat() and no symlinks. Then symlinks were added, and lstat() for those rare rare situations that you actually care if something is a symlink.

Clearly glob is using lstat() and not stat() because if I do glob --no-dirs * it will return symlinks to dirs, totally contrary to the spirit of how unix is supposed to work, and contrary to the rational behavior of scripts.

Yes, I do note that there is a --no-symlink option, but we don't want that, we want symlinks, just not links to dirs.

And yes there is a --follow-symlinks option, but this is ass-backward. the UNIX philosophy is that no program should be aware of symlinks unless you take special action to tell it to be aware. The whole point of symlinks is completely defeated if the default situation is that programs will not follow them by default.

Now, I suppose you COULD make an argument that glob ** syntax that does a recursive search, you might not want that to follow links by default, as per the UNIX find command. But when it comes to files that you've ALREADY decided to consider in your traversal, aka for example, files in the current directory that you are examining ANYWAY, this case you MUST consider the link's target, not the fact it's a link. These are two very different situations, the decision whether to go globbing WITHIN a discovered symlink directory, and the decision to REPORT and RETURN a link that is in fact a directory, when you asked for --no-dirs. To confound those two ideas is to produce stupid results. I may well decide I don't actually want to go recursive globbing withing symlinked dirs, but that by no means indicates that I want to get back results that are symlink dirs when I asked for --no-dirs. And don't think about --no-symlink because I don't want to exclude files symlinked.

So in summary, returning a directory as a result with --no-dirs merely because it's a link = bad, against unix philosophy. But refusing to go recursive searching WITHIN symlink directories = possibly a good idea.

How to reproduce

1. make a symlink to a directory in your cwd
2. type glob --no-dirs * and see that the symlink to a directory is returned.
3. Note that what should work fine: glob --no-dirs * | each { open $in } fails, when that should be a perfectly reasonable script.

Expected behavior

--no-dirs should never return dirs, even if they are symlinks to dirs.

Configuration

Start by reproducing glob --no-dirs * with a symlink to a directory, then locate the glob implementation and its handling of --no-dirs and symlink targets. Done means the command excludes symlinks whose targets are directories while still returning symlinks to files, without changing recursive traversal behavior.