[Issue 20104] core.atomic has no exchange function

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20104

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #1 from Dlang Bot  ---
@TurkeyMan updated dlang/druntime pull request #2729 "Added atomicExchange to
core.atomic" fixing this issue:

- Added atomicExchange to core.atomic

  Fix Issue 20104 - core.atomic has no exchange function

https://github.com/dlang/druntime/pull/2729

--


[Issue 15161] No way to express ref delegate

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15161

Harry Vennik  changed:

   What|Removed |Added

 CC||htven...@gmail.com

--


[Issue 20123] Impossible to disable post-increment/decrement semantics

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20123

--- Comment #1 from Manu  ---
Or a way to @disable the post-inc/dec semantics explicitly, so that I can
implement pre-inc/dec without opening the door for a race on the lowering.

--


[Issue 20123] New: Impossible to disable post-increment/decrement semantics

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20123

  Issue ID: 20123
   Summary: Impossible to disable post-increment/decrement
semantics
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: turkey...@gmail.com

D implements post-increment/decrement with a lowered expression.
According to the docs; (auto t = val, ++val, t)

I'm implementing C++'s atomic type, which implements `operator++` &
`operator--`, but I realised that the lowering is not atomic, and I seem to
have no way to implement the post-inc/dec operators explicitly such that I can
make them atomic.

To properly implement this library, I need a way to implement the post-int/dec
operators explicitly.

--


[Issue 20122] New: core.atomic.cas discards result on failure

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20122

  Issue ID: 20122
   Summary: core.atomic.cas discards result on failure
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: druntime
  Assignee: nob...@puremagic.com
  Reporter: turkey...@gmail.com

The implementation of `cas` discards the result when the compare fails.
This is a strange choice, and not desirable.

There needs to be additional overloads that actually return the result.

--


[Issue 17596] dmd d 2.073.2 and 2.074.1 interim generated dmd segfaults on FreeBSD 12-CURRENT

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17596

--- Comment #24 from Cy Schubert  ---
I've had no choice but to deorbit the dmd2 port as it has been marked broken
for more than 6 months. We can always resurrect it later though.

--


[Issue 18885] statfs struct was changed in FreeBSD 12

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18885

Cy Schubert  changed:

   What|Removed |Added

 CC||c...@freebsd.org

--- Comment #2 from Cy Schubert  ---
The FreeBSD port has been deleted.

--


[Issue 20121] New: "template lambda has no value" when assigned to struct

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20121

  Issue ID: 20121
   Summary: "template lambda has no value" when assigned to struct
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: simen.kja...@gmail.com

Lambdas don't correctly decay to functions or delegates when assigned via
opAssign, but do so correctly for regular functions and member functions, even
calling opAssign directly, and with property syntax:

unittest {
S s;
s.opAssign(i => i + 1); // Works
s.opAssign = i => i + 1; // Works
s = i => i + 1; // Fails (template lambda has no value)
}

struct S {
void opAssign(int delegate(int) fn) {}
void opAssign(int function(int) fn) {}
}

--


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

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12931

--- Comment #18 from Mathias LANG  ---
*** Issue 12930 has been marked as a duplicate of this issue. ***

--


[Issue 12930] static and the access modifiers aren't legal on the right-hand side of a function

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12930

Mathias LANG  changed:

   What|Removed |Added

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

--- Comment #2 from Mathias LANG  ---
At this point I don't think anyone will disagree that 12931 is the way to go.
Closing as duplicate in order to not confuse contributors looking for work :)

*** This issue has been marked as a duplicate of issue 12931 ***

--


[Issue 20024] "No property x for type Y" error not as helpful as it should be

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20024

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #2 from Dlang Bot  ---
dlang/dmd pull request #10301 "Issue 20024 - "No property x for type Y" error
not as helpful as it should be" was merged into master:

- 4d7895cba8933474c4b9c874068d298151de9e0c by Sebastian Wilzbach:
  Fix Issue 20024 - "No property x for type Y" error not as helpful as it
should be

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

--


[Issue 13059] Delete uses destructor rather than the delete operator

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13059

Mathias LANG  changed:

   What|Removed |Added

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

--- Comment #3 from Mathias LANG  ---
`delete` keyword is now officially deprecated.

--


[Issue 7491] import symbol name unavailable in class scope

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7491

Mathias LANG  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||pro.mathias.l...@gmail.com
 Resolution|--- |FIXED

--- Comment #7 from Mathias LANG  ---
D1 is gone

--


[Issue 2775] "private" ignored for templates

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=2775

Mathias LANG  changed:

   What|Removed |Added

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

--- Comment #7 from Mathias LANG  ---
The provided test cases now correctly error out.

--


[Issue 20120] libcurl.dll hangs when running std.net.curl unittests

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20120

--- Comment #3 from Rainer Schuetze  ---
Yeah, just tried to rebuild it, too. There are a lot of vulnerabilities fixed
since curl 7.48, so an update would be recommended. Maybe there is just
something wrong with the tests?

--


[Issue 20120] libcurl.dll hangs when running std.net.curl unittests

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20120

kinke  changed:

   What|Removed |Added

 CC||ki...@gmx.net

--- Comment #2 from kinke  ---
(In reply to Rainer Schuetze from comment #1)
> Might be related to the version of libcurl: LDC comes with version 7.48.0,
> and the regression happened when upgrading from 7.47.1 to 7.51.0

Yes, exactly because we get CI failures with newer libcurl versions. I
initially thought it may be specific to how it is built (compilation options,
linked MSCRT etc.), so I tried to build the last libcurl versions myself [a
while ago], but failed to produce a working one.

--


[Issue 20120] libcurl.dll hangs when running std.net.curl unittests

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20120

--- Comment #1 from Rainer Schuetze  ---
Might be related to the version of libcurl: LDC comes with version 7.48.0, and
the regression happened when upgrading from 7.47.1 to 7.51.0

--


[Issue 20120] New: libcurl.dll hangs when running std.net.curl unittests

2019-08-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20120

  Issue ID: 20120
   Summary: libcurl.dll hangs when running std.net.curl unittests
   Product: D
   Version: D2
  Hardware: All
OS: Windows
Status: NEW
  Severity: regression
  Priority: P1
 Component: installer
  Assignee: nob...@puremagic.com
  Reporter: r.sagita...@gmx.de

It seems the distribuuted libcurl.dll is broken since 2.072: executing

dmd -unittest -main -run \std\net\curl.d

freezes until some timeout expires after a couple of minutes. The same happens
with -m64.

The unittests pass with the DLL that comes with dmd 2.071 or the ones from the
LDC distro.

--