[Issue 17810] New: Add wcwidth/wcswidth equivalents to std.uni

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17810

  Issue ID: 17810
   Summary: Add wcwidth/wcswidth equivalents to std.uni
   Product: D
   Version: D2
  Hardware: x86
OS: Mac OS X
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: phobos
  Assignee: nob...@puremagic.com
  Reporter: jrdemail2000-dl...@yahoo.com

Enhancement request: Add the equivalents of the POSIX wcwidth/wcswidth
functions to std.uni.

These functions calculate the expected cell width of a wchar_t or wchar string.
This is the normal character width in fixed width fonts. It is useful in
command-line apps and other terminal displays where fixed width fonts are
commonly used. Generally, CJK characters are two cells wide, most other
characters are one cell wide. Cell width properties are part of the unicode
standard.

--

[Issue 2538] Final method is not involved in inteface method resolution

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=2538

John Hall  changed:

   What|Removed |Added

 CC||john.michael.h...@gmail.com

--- Comment #11 from John Hall  ---
This issue is discussed on the forum here:
https://forum.dlang.org/post/awkmkusrqnzdkyeyx...@forum.dlang.org

--

[Issue 9776] Make raw write mode the default

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9776

--- Comment #14 from anonymous4  ---
Not documented that std.file doesn't use C stdio and is not compatible with it
(and not intended) and no remark to not mix it with stdio as was suggested
here.

--

[Issue 15399] unaligned pointers are not @safe

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=15399

ag0ae...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||ag0ae...@gmail.com
 Resolution|FIXED   |---

--- Comment #5 from ag0ae...@gmail.com ---
Reopening because these very slight variations are still accepted:

1) hosts[n] = Unaligned(0, new Victim);
2) Unaligned u = { p: new Victim }; hosts[n] = u;

--

[Issue 9776] Make raw write mode the default

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9776

--- Comment #13 from Vladimir Panteleev  ---
(In reply to anonymous4 from comment #12)
> Not documented though.

How so? The documentation for stdioOpenmode says "range or string represting
the open mode (with the same semantics as in the C standard library fopen
function)", so the defaults for unspecified options are left to the C standard
library implementation. AIUI, it's not part of the language because on POSIX
binary and text modes behave the same.

--

[Issue 5866] std.math.sin(float), std.math.cos(float) to return float

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=5866

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||razvan.nitu1...@gmail.com
 Resolution|--- |WORKSFORME

--- Comment #6 from RazvanN  ---
The code in the original bug report now compiles successfully on git HEAD
ubuntu 16.04. Closing as WORKSFORME.

--

[Issue 17809] New: "this" is implicitly captured by template with alias parameter

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17809

  Issue ID: 17809
   Summary: "this" is implicitly captured by template with alias
parameter
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: john.loughran.col...@gmail.com

template A()
{
auto A() { return this; }
}

template B(alias a)
{
auto B() { return this; }
}

struct S
{
int a;

// Error: 'this' is only defined in non-static member functions, not A
alias foo0 = A!();

// OK ??? I don't think this should work
alias foo1 = B!(a);
}

--

[Issue 17809] "this" is implicitly captured by template with alias parameter

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17809

John Colvin  changed:

   What|Removed |Added

   Keywords||accepts-invalid

--

[Issue 12171] Parenthesis-less call fails in static array length context

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=12171

--- Comment #3 from RazvanN  ---
Seeing as the platform on which the bug was reported is windows, I modified to
WORKSFORME, if anyone has a windows platform, please try the example and reopen
if necessary.

--

[Issue 12171] Parenthesis-less call fails in static array length context

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=12171

RazvanN  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

--

[Issue 12171] Parenthesis-less call fails in static array length context

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=12171

RazvanN  changed:

   What|Removed |Added

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

--- Comment #2 from RazvanN  ---
This code successfully compiles on git HEAD ubuntu 16.04. Closing as fixed.

--

[Issue 11729] protected toString causes strange error message

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=11729

--- Comment #5 from RazvanN  ---
There is nothing wrong with the compiler message. The toString method is not
visible outside the module it was declared so the template constraint
hasToString!(T, Char) fails (as it should). I think we should close this.

--

[Issue 11729] protected toString causes strange error message

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=11729

--- Comment #4 from anonymous4  ---
And I think this can't be patched in phobos: formatObject can't work with
protected toString, hence it must be skipped, which results in the generic
template mismatch error.

--

[Issue 9626] More precise error message in some cases when failed template constraint

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9626

anonymous4  changed:

   What|Removed |Added

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

--

[Issue 11729] protected toString causes strange error message

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=11729

anonymous4  changed:

   What|Removed |Added

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

--- Comment #3 from anonymous4  ---
Issue 9626 is for compiler diagnostic. But I'm not sure we want to patch this
case by case instead of improving diagnostic in compiler.

--

[Issue 17808] New: VisualD doesn't work if Visual Studio is installed to non-ASCII path

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17808

  Issue ID: 17808
   Summary: VisualD doesn't work if Visual Studio is installed to
non-ASCII path
   Product: D
   Version: D2
  Hardware: x86_64
OS: Windows
Status: NEW
  Severity: minor
  Priority: P1
 Component: visuald
  Assignee: nob...@puremagic.com
  Reporter: karol.m.stas...@gmail.com

Created attachment 1656
  --> https://issues.dlang.org/attachment.cgi?id=1656=edit
Build script with mangled paths

Windows 10, Polish locale, Visual Studio Community 2015, VisualD 0.45.1.

Visual Studio is installed at D:\Pliki programów (x86)\Microsoft Visual Studio
14.0 

When I run the installer for VisualD, it detects that I have VS2015 installed,
but then it proceeds to install the extension to D:\Pliki program�
(x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions

Note the invalid character.

After the installation, Visual Studio listed the extension on the extension
list, but the extension obviously did not load. I was unable to create any D
projects or change D-related settings.

After I moved the extension manually, it loaded and I could create a new
project, but then it still wouldn't work: 
- running the x86 target displays a console window for a fraction of a second,
shows the following in the output, and does nothing else:

C:\Windows\SysWOW64\kernel32.dll unloaded.
C:\Windows\SysWOW64\dbghelp.dll unloaded.
The thread 0x7a4 has exited with code 0 (0x0).
The thread 0x29c has exited with code 0 (0x0).
The thread 0xf4 has exited with code 0 (0x0).
The program '[2596] ConsoleApp1.exe' has exited with code 0 (0x0).

- as for the x64 target, the build script (x64\Debug\ConsoleApp1.build.cmd)
contains wrong paths (two different ones!) as well, so VS cannot build
anything. I've attached the file.

VS failed to produce any executables.

--

[Issue 11729] protected toString causes strange error message

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=11729

anonymous4  changed:

   What|Removed |Added

   Keywords||diagnostic

--- Comment #2 from anonymous4  ---
I suppose something like this:

class A
{
protected override string toString(){ return null; }
}
void f()
{
import std.stdio;
write(new A);
}
std/format.d(3450): Error: template instance
std.format.formatObject!(LockingTextWriter, A, char) does not match template
declaration formatObject(Writer, T, Char)(ref Writer w, ref T val, ref const
FormatSpec!Char f) if (hasToString!(T, Char))

--

[Issue 4555] Double newlines with std.file.readText

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4555

--- Comment #5 from RazvanN  ---
Since this one was reported originally, I think it would make more sense to
mark 9776 as a duplicate of this one. Either way, the issues reference each
other so I guess anything works.

--

[Issue 9776] Make raw write mode the default

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9776

anonymous4  changed:

   What|Removed |Added

 CC||bearophile_h...@eml.cc

--- Comment #11 from anonymous4  ---
*** Issue 4555 has been marked as a duplicate of this issue. ***

--

[Issue 4555] Double newlines with std.file.readText

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4555

anonymous4  changed:

   What|Removed |Added

 Resolution|WONTFIX |DUPLICATE

--- Comment #4 from anonymous4  ---


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

--

[Issue 9776] Make raw write mode the default

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9776

--- Comment #12 from anonymous4  ---
(In reply to Vladimir Panteleev from comment #8)
> Whether you agree or disagree, everything here works "as designed"

Not documented though.

--

[Issue 4555] Double newlines with std.file.readText

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=4555

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||razvan.nitu1...@gmail.com
 Resolution|--- |WONTFIX

--- Comment #3 from RazvanN  ---
This issue is the same as 9776. The decision for 9776 was to close it as
WONTFIX. Applying the same procedure to this one.

--

[Issue 13546] std.functional.not for arrays too

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13546

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--

[Issue 13546] std.functional.not for arrays too

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13546

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #1 from RazvanN  ---
This seems like a corner case for arrays. Its implementation would lead to more
problems than cases where things get simplified.

If you want to work with boolean arrays you could either use the solution in
the bug report or you could always use BitArrays. Also there is the problem of
where should the function `not` be located after this change, because all the
functions in std.functional work solely with functions.

In my opinion, this should be closed as WONTFIX.

--

[Issue 11729] protected toString causes strange error message

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=11729

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #1 from RazvanN  ---
Could you please offer an example and the output? The issue description is very
vague.

--

[Issue 1425] Feature Request: call stack reflection

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=1425

RazvanN  changed:

   What|Removed |Added

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

--- Comment #3 from RazvanN  ---
I do not know what the situation was back then with assert, but now, the simple
builtin assert is enough to get a stack trace. It seems like `assert` is a
wrapper which implements the features requested so, in my opinion this should
be closed. Reopen if I misunderstand something.

Example:

void foo(int p1, int p2) 
{
assert(p1 == p2);
}

void bar(int p1, int p2) 
{
foo(p1, p2);
}

void main()
{
int var5 = 1;
int var6 = 2;

bar(var5, var6);
}

Prints:

core.exception.AssertError@fast.d(23): Assertion failure

??:? _d_assertp [0x425d65]
??:? void fast.foo(int, int) [0x425c86]
??:? void fast.bar(int, int) [0x425c94]
??:? _Dmain [0x425cb0]

--

[Issue 17788] MSCOFF: TLS broken when linking with linker from VS2017 15.3.1

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17788

--- Comment #1 from github-bugzi...@puremagic.com ---
Commits pushed to stable at https://github.com/dlang/druntime

https://github.com/dlang/druntime/commit/07a25c9ec1deb7bcdf45d37d51a5b18d91fd1083
fix issue 17788: MSCOFF: with VS2017 15.3.1 segment .tls is no longer written
to a separate image section, so _tls_start and _tls_end no longer happen to
work as both __gshared and TLS section offsets.

https://github.com/dlang/druntime/commit/e07fa031919579bd2b48f1f7ebb634061bd3daca
Merge pull request #1910 from rainers/issue17788

fix issue 17788: MSCOFF: TLS broken with VS2017 15.3.1

--

[Issue 3831] writeln of a delegate typeid

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=3831

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com
  Component|phobos  |dmd

--- Comment #7 from RazvanN  ---
This is a dmd bug, not a phobos one. Changing the component to dmd.

--

[Issue 15489] regex - `(..).*\1` doesn't match "axxxx"

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=15489

Dmitry Olshansky  changed:

   What|Removed |Added

  Component|dmd |phobos
   Assignee|nob...@puremagic.com|dmitry.o...@gmail.com

--

[Issue 13532] std.regex performance (enums; regex vs ctRegex)

2017-09-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13532

--- Comment #7 from Dmitry Olshansky  ---
https://github.com/dlang/phobos/pull/5722

--