[Issue 22541] DIP1000: Resolve ambiguity of ref-return-scope parameters

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22541

--- Comment #4 from Walter Bright  ---
Where I'd like to go is only allow "return ref" or "return scope". In the
meantime, backwards compatibility will do for the first iteration.

--


[Issue 22549] importC: float literal should support leading zero

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22549

--- Comment #4 from Basile-z  ---
also no reason to target stable(In reply to Basile-z from comment #3)
> the fix affects the specs https://dlang.org/spec/lex.html#LeadingDecimal,
> hence everything that would be based on them.
> 
> I suggest to only allow leading zeroes in importC mode.

sorry about that comment, as explained here
https://issues.dlang.org/show_bug.cgi?id=3251, that is not required.

--


[Issue 22549] importC: float literal should support leading zero

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22549

Basile-z  changed:

   What|Removed |Added

 CC||b2.t...@gmx.com

--- Comment #3 from Basile-z  ---
the fix affects the specs https://dlang.org/spec/lex.html#LeadingDecimal, hence
everything that would be based on them.

I suggest to only allow leading zeroes in importC mode.

--


[Issue 22552] moveEmplace wipes context pointer of nested struct contained in non-nested struct

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22552

kinke  changed:

   What|Removed |Added

 CC||ki...@gmx.net

--- Comment #1 from kinke  ---
(In reply to Stanislav Blinov from comment #0)
> That's because moveEmplace simply blits NotNested.init into a. Instead it
> probably should move things fieldwise and avoid wiping context pointers in
> fields that are nested structs.

Blitting the whole thing at once is still fine, but the problem arises with the
T.init reset of the source instance. It would probably really have to reset the
fields recursively in order not to clear any context pointers. There should IMO
still be a fast path for the very common case of no nested context pointers.

--


[Issue 22553] ImportC: undefined identifier `__uint128_t`

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22553

dave287...@gmail.com changed:

   What|Removed |Added

   Keywords||ImportC

--


[Issue 22553] New: ImportC: undefined identifier `__uint128_t`

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22553

  Issue ID: 22553
   Summary: ImportC: undefined identifier `__uint128_t`
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: major
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: dave287...@gmail.com

Clang (and probably gcc as well) have an extension type of __uint128_t which is
a 128 bit unsigned integer.  on macOS for arm64 transitively includes
a header that uses this type, leading to compilation failure.

--


[Issue 22552] New: moveEmplace wipes context pointer of nested struct contained in non-nested struct

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22552

  Issue ID: 22552
   Summary: moveEmplace wipes context pointer of nested struct
contained in non-nested struct
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: druntime
  Assignee: nob...@puremagic.com
  Reporter: stanislav.bli...@gmail.com

import core.lifetime;

void main()
{
int i;

struct Nested
{
~this() { ++i; }
}

static struct NotNested
{
Nested n;
}

auto a = NotNested(Nested()); // when this is destructed things go boom...

NotNested b = void;
moveEmplace(a, b); // ...because this wipes context pointer in a.n
} // segmentation fault

---

That's because moveEmplace simply blits NotNested.init into a. Instead it
probably should move things fieldwise and avoid wiping context pointers in
fields that are nested structs.

--


[Issue 22549] importC: float literal should support leading zero

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22549

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #2 from Dlang Bot  ---
@dkorpel created dlang/dmd pull request #13371 "Fix issue 22549 - float literal
should support leading zero" fixing this issue:

- Fix issue 22549 - float literal should support leading zero

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

--


[Issue 7227] [:] as empty associative array literal, plus warning for null

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7227

Nick Treleaven  changed:

   What|Removed |Added

 CC||n...@geany.org
   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=10535

--


[Issue 10535] [AA] Add a function to druntime which returns an empty AA

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=10535

Nick Treleaven  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=7227

--


[Issue 20907] [DIP1000] Unittest fails when duplicated

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20907

--- Comment #4 from Dlang Bot  ---
dlang/dmd pull request #13370 "Add opApply test case for issue 20907" was
merged into master:

- de2d05e6a70ddbcae1d03bd75e45755e863ca7c9 by dkorpel:
  Add opApply test case for issue 20907

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

--


[Issue 20907] [DIP1000] Unittest fails when duplicated

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20907

Dennis  changed:

   What|Removed |Added

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

--- Comment #3 from Dennis  ---
This compiles now with -preview=dip1000 since "Rework fix for attribute based
opApply overloads (issue 15624) #13226":
https://github.com/dlang/dmd/pull/13226

--


[Issue 22551] New: DWARF: functions inside structs are not being recognized as member functions

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22551

  Issue ID: 22551
   Summary: DWARF: functions inside structs are not being
recognized as member functions
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Keywords: DebugInfo
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: cont...@lsferreira.net

In DMD DWARF generator, DW_TAG_subprogram is not a parent of
DW_TAG_structure_type and therefore it is not considered members of the struct.

--


[Issue 22518] [dip1000] return without scope/ref not specified

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22518

--- Comment #2 from Dlang Bot  ---
@dkorpel updated dlang/dmd pull request #13317 "Make `return` equivalent to
`return scope` for issue 22518" mentioning this issue:

- Make `return` equivalent to `return scope` for issue 22518

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

--


[Issue 21719] [REG 2.072] "auto" methods of classes do not infer attributes correctly.

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21719

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #4 from Dlang Bot  ---
dlang/dmd pull request #13308 "Fix Issue 21719 -  [REG 2.072] "auto" methods of
classes do not infer attributes correctly." was merged into master:

- 1b859425aae85e63554c230d106393c2bb83592c by RazvanN7:
  Fix Issue 21719 - [REG 2.072] auto methods of classes do not infer attributes
correctly.

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

--


[Issue 21897] Semicolon inside quotes in path variable causes range violation in pipedmd

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21897

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||r.sagita...@gmx.de
 Resolution|--- |FIXED

--- Comment #1 from Rainer Schuetze  ---
fix finally released in
https://github.com/dlang/visuald/releases/tag/v1.2.0-rc1

--


[Issue 21877] VS2019 crash with "Show parameter storage class at call site"

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21877

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||r.sagita...@gmx.de
 Resolution|--- |FIXED

--- Comment #1 from Rainer Schuetze  ---
fix finally released in
https://github.com/dlang/visuald/releases/tag/v1.2.0-rc1

--


[Issue 21894] Memory leak in DMD semantic server.

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21894

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||r.sagita...@gmx.de
 Resolution|--- |FIXED

--- Comment #1 from Rainer Schuetze  ---
hopefully fixed by building the server with dmd instead of LDC (the latter
doesn't support precise scanning of the DATA segment) in
https://github.com/dlang/visuald/releases/tag/v1.2.0-rc1

In addition, there is now an option to wipe most data if some memory threshold
is exceeded.

--


[Issue 21710] Code Completion doesn't work if compiler path contains a white space

2021-11-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21710

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||r.sagita...@gmx.de
 Resolution|--- |FIXED

--- Comment #1 from Rainer Schuetze  ---
fix finally released in
https://github.com/dlang/visuald/releases/tag/v1.2.0-rc1

--