Awesome (I made no claims of expertise about the details of the call
semantics). I agree any multi-call scenario would among other things not be
atomic. Though, I’m not sure that’s what you mean by hoodwinked.
That last suggestion is exactly one I also made (simply improve the error text)
and I
(I originally overlooked your mention of a race)
... by the way, I'm curious whether bash is systematically coded to
defend against these kinds of races and whether they are in fact a
material concern?
Notwithstanding, in this particular case, we're talking only about
generating an error mes
On Sun, 29 May 2022, 06:56 AA via Bug reports for the GNU Bourne Again
SHell, wrote:
> Maybe the concern is that any additional calls (such as checking for path
> existence) may have unintended consequences [but that] seems unlikely.
>
> Therefore, IMHO it is very hard to argue with the fact that