[Issue 18357] New: can break immutable with postblit

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

  Issue ID: 18357
   Summary: can break immutable with postblit
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Keywords: accepts-invalid
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: ag0ae...@gmail.com


struct S
{
int* x;
this(this) @safe { *x = 13; }
}

void main() @safe
{
immutable int* x = new int(42);
assert(*x == 42); /* passes */
auto s = immutable S(x);
auto s2 = s; /* should be rejected */
assert(*x == 42); /* fails */
}


--


[Issue 18356] no property 'tempCString' for type 'const(char)[]'

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

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Seb  ---
This was fixed in https://github.com/dlang/phobos/pull/6079 and is also a
duplicate of 18316

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

--


[Issue 18316] std.net.curl.SMTP.mailTo fails to compile

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

Seb  changed:

   What|Removed |Added

 CC||bitwo...@qq.com

--- Comment #2 from Seb  ---
*** Issue 18356 has been marked as a duplicate of this issue. ***

--


[Issue 18134] BitArray <<= broken when length % 32 = 0

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

Jakub Łabaj  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||uaaabbj...@gmail.com

--- Comment #2 from Jakub Łabaj  ---
Seems like it was wrong only for multiples of size_t.sizeof. I made a PR fixing
this: https://github.com/dlang/phobos/pull/6110.

--


[Issue 18134] BitArray >>= broken when length % size_t.sizeof = 0

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

Jakub Łabaj  changed:

   What|Removed |Added

Summary|BitArray <<= broken when|BitArray >>= broken when
   |length % 32 = 0 |length % size_t.sizeof = 0

--


[Issue 18357] can break immutable with postblit

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

Ketmar Dark  changed:

   What|Removed |Added

 CC||ket...@ketmar.no-ip.org

--


[Issue 15509] IAllocator must be exposed via a reference counted struct

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

Seb  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||greensunn...@gmail.com
 Resolution|--- |FIXED

--- Comment #5 from Seb  ---
This has been fixed by https://github.com/dlang/phobos/pull/5921

See also 

https://dlang.org/changelog/pending.html#std-experimental-allocator-rciallocator

--


[Issue 18134] BitArray >>= broken when length % (8 * size_t.sizeof) == 0

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

Jakub Łabaj  changed:

   What|Removed |Added

Summary|BitArray >>= broken when|BitArray >>= broken when
   |length % size_t.sizeof = 0  |length % (8 *
   ||size_t.sizeof) == 0

--


[Issue 18133] BitArray prints bits in wrong order

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

Jakub Łabaj  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

--- Comment #3 from Jakub Łabaj  ---
Because this isn't a printing bug, but rather problem with poorly documented
constructor, I renamed the issue name.

--


[Issue 18133] BitArray constructors are poorly documented.

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

Jakub Łabaj  changed:

   What|Removed |Added

Summary|BitArray prints bits in |BitArray constructors are
   |wrong order |poorly documented.

--


[Issue 18351] integrate dub changelog with changed.d tool

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

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
A first step:

https://github.com/dlang/tools/pull/302

--


[Issue 18351] integrate dub changelog with changed.d tool

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

--- Comment #2 from Seb  ---
And for deploying automatically to the pending changelog:
https://github.com/dlang/dlang.org/pull/2163

--


[Issue 18358] New: No links to the deprecation page

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

  Issue ID: 18358
   Summary: No links to the deprecation page
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dlang.org
  Assignee: nob...@puremagic.com
  Reporter: pastuho...@gmail.com

It seems that the only way to see https://dlang.org/deprecate.html is a direct
link. It doesn't present in a site menu and seems not to have any internal
links. Wiki is also empty.

I was completely unaware this page ever exists until occasionally stumbled upon
it somewhere in the forums.

--


[Issue 18133] BitArray constructors are poorly documented.

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

Jakub Łabaj  changed:

   What|Removed |Added

   Assignee|nob...@puremagic.com|uaaabbj...@gmail.com

--


[Issue 18134] BitArray >>= broken when length % (8 * size_t.sizeof) == 0

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

Jakub Łabaj  changed:

   What|Removed |Added

   Assignee|nob...@puremagic.com|uaaabbj...@gmail.com

--


[Issue 18359] New: writeln and synchronized classes don't sync properly

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

  Issue ID: 18359
   Summary: writeln and synchronized classes don't sync properly
   Product: D
   Version: D2
  Hardware: x86_64
   URL: http://dlang.org/
OS: Windows
Status: NEW
  Severity: normal
  Priority: P3
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: weltenst...@gmail.com

Created attachment 1679
  --> https://issues.dlang.org/attachment.cgi?id=1679&action=edit
Synchronized fails

Using this code:

import
core.thread,
std.stdio,
std.range,
std.algorithm;

void main(){
Thread[] threads;
iota(0,20).each!((i){
threads ~= new Thread({
writeln(i);
});
});
foreach(t; threads)
t.start;
foreach(t; threads)
t.join;
}

writeln gets confused, printing this:
0

2
3
3
4
5
5
6
7
8
8
9
10
11
12
13
14
14
15
16
18
19
17

It works fine with LDC2.


Additionally, when running the following through a Visual Studio Code terminal:

while(true)
writeln("something");

(using code-d, I think it embeds a PowerShell) writeln breaks with an access
violation:

>[error] object.Error@(0): Access Violation
>
>0x0053FA35 in write
>0x00539FF5 in fflush
>0x0046A9EA in @safe void std.stdio.File.LockingTextWriter.put!(char).put(char) 
>at src\phobos\std\stdio.d(2876)
>0x00435867 in @safe void 
>std.range.primitives.doPut!(std.stdio.File.LockingTextWriter, char).doPut(ref 
>std.stdio.File.LockingTextWriter, ref char) at 
>src\phobos\std\range\primitives.d(287)
>...


It also looks like synchronized class does not synchronize method bodies
correctly. I couldn't get a small example to fail, but I'll attach 180 lines
that do. It works when building with LDC or wrapping the method bodies in
synchronized(this){...}. (It also shows writeln going crazy)


Using Windows 10 x64, DMD32 v2.078.1, building with dub and rdmd

--


[Issue 18359] writeln and synchronized classes don't sync properly

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

Robert Luger  changed:

   What|Removed |Added

 CC||weltenst...@gmail.com

--


[Issue 18359] writeln and synchronized classes don't sync properly

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

--- Comment #1 from Robert Luger  ---
Tried it with --arch=x86_64/-m64, does not happen there. Only seems to affect
32 bit binaries.

--


[Issue 18355] [Areas of D usage]

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

--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dlang.org

https://github.com/dlang/dlang.org/commit/5cd30438c21dcc0efd41bb0e04f476176bcbe8bc
Fix Issue 18355 - [Areas of D usage]

https://github.com/dlang/dlang.org/commit/8c4cdeafd4e5dce01486d828bb3a4ea8b1227da7
Merge pull request #2160 from wilzbach/fix-18355

Fix Issue 18355 - [Areas of D usage] - broken link
merged-on-behalf-of: Petar Kirov 

--