phobo's std.file is completely broke!

[Jonathan M Davis]

On Saturday, September 15, 2018 5:47:08 PM MDT tide via Digitalmars-d wrote:
> On Saturday, 15 September 2018 at 18:33:52 UTC, bachmeier wrote:
> > On Saturday, 15 September 2018 at 13:54:45 UTC, tide wrote:
> >> On Friday, 14 September 2018 at 19:17:58 UTC, bachmeier wrote:
> >>> On Friday, 14 September 2018 at 19:06:14 UTC, Josphe Brigmo
> >>>
> >>> wrote:
> >>>> For very long file names it is broke and every command
> >>>> fails. These paths are not all that long but over 256 limit.
> >>>> (For windows)
> >>>
> >>> Please file a bug report with reproducible examples if you
> >>> believe it's a bug.
> >>
> >> I feel people need to stop saying this.
> >
> > That's how things are done in this project (and most projects).
> > Anyone not liking that is out of luck. I don't use any open
> > source projects that use vague posts to a forum to report bugs.
>
> That's how they are, but if you are going to say silly things. At
> least take the initiative on yourself to go see if the bug
> already exists. Odds are it has probably already been reported,
> someone making a forums post about it is just able the next step
> after the bug report has been sitting in the queue for 4+ years.
>
> The problem isn't reporting the bug, it's that for D, no one is
> managing bugzilla. It seems to be the conclusion was reached that
> this is not a bug and won't be fixed. That could have been done a
> long time ago and closed the bug. Or at least I think Jonathan is
> part of the Dlang organization. Not sure, hard to tell who is and
> isn't on these boards.

The issue was reported in bugzilla quite some time ago.

https://issues.dlang.org/show_bug.cgi?id=8967

However, while Walter's response on it basically indicates that we should
just close it as "won't fix," we never actually did - which is something
that probably happens too often. There was further discussion in there that
never went anywhere. What we should probably do is ensure that the std.file
documentation is clear about the issue and count that as the fix. Either
way, I think that it's pretty clear that the documentation needs to be
improved.

As for figuring out who is "officially" part of the dlang org (or at least
has the rights to merge PRs from at least one dlang repo), you can look here

https://github.com/orgs/dlang/people

though it's possible to hide your membership, so while I see 59 members when
I look at it while signed in, if I look at it while not signed in, I see
only 40.

- Jonathan M Davis