[Issue 16709] [Reg 2.068] Error: common.to at common.d conflicts with common.to at common.d

2020-02-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16709

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #3 from Dlang Bot  ---
@WalterBright created dlang/dmd pull request #10793 "fix Issue 16709 - [Reg
2.068] Error: common.to at common.d conflicts …" fixing this issue:

- fix Issue 16709 - [Reg 2.068] Error: common.to at common.d conflicts with
common.to at common.d

https://github.com/dlang/dmd/pull/10793

--


[Issue 16709] [Reg 2.068] Error: common.to at common.d conflicts with common.to at common.d

2020-02-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16709

Dlang Bot  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Dlang Bot  ---
dlang/dmd pull request #10793 "fix Issue 16709 - [Reg 2.068] Error: common.to
at common.d conflicts …" was merged into master:

- 340807a16dd14c7f61d1df9d3ded3aecd59263e0 by Walter Bright:
  fix Issue 16709 - [Reg 2.068] Error: common.to at common.d conflicts with
common.to at common.d

https://github.com/dlang/dmd/pull/10793

--


[Issue 20584] New: std.process documentation really needs work

2020-02-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20584

  Issue ID: 20584
   Summary: std.process documentation really needs work
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dlang.org
  Assignee: nob...@puremagic.com
  Reporter: turkey...@gmail.com

I have spent about an hour reading the std.process documentation and messing
around, but I can't make heads or tails of it.

I'm trying to work out how to spawn a process and manage the input/output
streams.
There appear to be functions that are made for this, but the docs are confusing
and examples are not helpful.

Consider `executeShell`, it returns `auto`, which appears to be an object, but
who knows what members it has? It has at least `status` and `output`... but how
do I get the stderr stream which it says it also captures?

I don't think any function in the std lib should ever return `auto`, it's
hostile to documentation.

Looking at the source code, it's not easy to follow at all.

pipeProcess, which looks like it might help me, another `auto` result, and the
examples are weird; it looks like it waits for the program to finish on scope
exit, but it scrapes the stdout and stderr streams while the program is still
running (and may not be finished?)

I am getting almost no value out of anything in this whole doco. Someone should
consider it from a what-a-user-wants-to-achieve point of view, make useful
examples, and get rid of the `auto`s in the api.

I should have spent seconds on this task, but I've been staring at it for
hours, and it's still not clear what I'm supposed to do.

--


[Issue 12931] Make const, immutable, inout, and shared illegal as function attributes on the left-hand side of a function

2020-02-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12931

Mathias LANG  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||pro.mathias.l...@gmail.com
 Resolution|--- |WONTFIX

--- Comment #22 from Mathias LANG  ---
So after raising a PR, it turns out Walter is against it:
https://github.com/dlang/dmd/pull/10757#issuecomment-586849786

Marking as "WONTFIX" as a result. Feel free to chime in on Github if you feel
strongly about it.

--