[Issue 19898] ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19898

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #2 from Dlang Bot  ---
dlang/dmd pull request #9855 "fix Issue 19898 - ICE: in sizemask at
dmd/mtype.d(2563): Assertion failure" was merged into stable:

- 30ba4bc7a509283f8957fc084e8b56e94c76369c by Iain Buclaw:
  fix Issue 19898 - ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

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

--


[Issue 19754] cast() sometimes yields lvalue, sometimes yields rvalue

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19754

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #11 from Dlang Bot  ---
dlang/dmd pull request #9505 "Fix Issue 19754 - cast() sometimes yields lvalue,
sometimes yields rvalue" was merged into master:

- 91e7151838a703e9c31cf308f3711ddee47c86e6 by RazvanN7:
  Fix Issue 19754 - cast() sometimes yields lvalue, sometimes yields rvalue

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

--


[Issue 19513] Use sched_getaffinity(2) to get the number of CPU cores if available

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19513

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #1 from Dlang Bot  ---
@kubo39 created dlang/phobos pull request #7030 "Fix Issue 19513 - Use
sched_getaffinity(2) to get the number of CPU cores if abailable" fixing this
issue:

- Fix Issue 19513 - Use sched_getaffinity(2) to get the number of CPU
  cores if available

  Currently std.parallelism.totalCPUs is implemented by
  sysconf(_SC_NPROCESSORS_ONLN) on Posix platoform. However, on GNU/Linux,
  usable number of processors may be restricted if a process runs in
  container. In case it's better to use sched_getaffinity(2).

  ref: http://man7.org/linux/man-pages/man1/nproc.1.html

https://github.com/dlang/phobos/pull/7030

--


[Issue 19897] dinterpret.d:6439: Internal Compiler Error: null field

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19897

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #2 from Dlang Bot  ---
dlang/dmd pull request #9854 "fix Issue 19897 - dinterpret.d:6439: Internal
Compiler Error: null field" was merged into stable:

- 9aa363e2de98290855cfcc5e56d3a8d0c6cf788a by Iain Buclaw:
  fix Issue 19897 - dinterpret.d:6439: Internal Compiler Error: null field

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

--


[Issue 19895] Floating point exception casting zero length array

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19895

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #3 from Dlang Bot  ---
dlang/dmd pull request #9856 "Fix Issue 19895 - Floating point exception
casting zero length array" was merged into stable:

- 25b6ff6487f3cdb8b984dee90ded33ef1b244bda by Hiroki Noda:
  Fix Issue 19895 - Floating point exception casting zero length array

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

--


[Issue 19890] ICE: Segmentation fault with negative array size

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19890

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #5 from Dlang Bot  ---
dlang/dmd pull request #9840 "fix Issue 19890 - ICE: Segmentation fault with
negative array size" was merged into master:

- fb7814cc95e504503f6d6f94f3fc4ed2b73715b7 by Iain Buclaw:
  fix Issue 19890 - ICE: Segmentation fault with negative array size

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

--


[Issue 19825] Memory corruption involving lazy variadic, stdio and json

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19825

Suleyman Sahmi (سليمان السهمي)  changed:

   What|Removed |Added

 CC||sahmi.soulaim...@gmail.com
   Assignee|nob...@puremagic.com|sahmi.soulaim...@gmail.com

--


[Issue 19895] Floating point exception casting zero length array

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19895

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #2 from Dlang Bot  ---
@kubo39 created dlang/dmd pull request #9856 "Fix Issue 19895 - Floating point
exception casting zero length array" fixing this issue:

- Fix Issue 19895 - Floating point exception casting zero length array

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

--


[Issue 19898] ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19898

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #1 from Dlang Bot  ---
@ibuclaw created dlang/dmd pull request #9855 "fix Issue 19898 - ICE: in
sizemask at dmd/mtype.d(2563): Assertion failure" fixing this issue:

- fix Issue 19898 - ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

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

--


[Issue 19897] dinterpret.d:6439: Internal Compiler Error: null field

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19897

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #1 from Dlang Bot  ---
@ibuclaw created dlang/dmd pull request #9854 "fix Issue 19897 -
dinterpret.d:6439: Internal Compiler Error: null field" fixing this issue:

- fix Issue 19897 - dinterpret.d:6439: Internal Compiler Error: null field

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

--


[Issue 19898] ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19898

Iain Buclaw  changed:

   What|Removed |Added

 CC||ibuc...@gdcproject.org

--


[Issue 19898] New: ICE: in sizemask at dmd/mtype.d(2563): Assertion failure

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19898

  Issue ID: 19898
   Summary: ICE: in sizemask at dmd/mtype.d(2563): Assertion
failure
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: critical
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: ibuc...@gdcproject.org

void f (__vector(int[4]) n)
{
  foreach (i; 0..n)
n;
}

--


[Issue 19897] dinterpret.d:6439: Internal Compiler Error: null field

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19897

Iain Buclaw  changed:

   What|Removed |Added

 CC||ibuc...@gdcproject.org

--


[Issue 19896] [internals] Represent string and arrays as sparse literals

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19896

Iain Buclaw  changed:

   What|Removed |Added

 CC||ibuc...@gdcproject.org

--


[Issue 19897] dinterpret.d:6439: Internal Compiler Error: null field

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19897

Iain Buclaw  changed:

   What|Removed |Added

   Keywords||ice

--


[Issue 16643] CTFE internal error with null

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16643

Iain Buclaw  changed:

   What|Removed |Added

 CC||ibuc...@gdcproject.org
   Severity|minor   |critical

--


[Issue 19897] New: dinterpret.d:6439: Internal Compiler Error: null field

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19897

  Issue ID: 19897
   Summary: dinterpret.d:6439: Internal Compiler Error: null field
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: critical
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: ibuc...@gdcproject.org

struct S { char[0] x; }
const a = S('a');
const char c = a.x;

--


[Issue 19896] New: [internals] Represent string and arrays as sparse literals

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19896

  Issue ID: 19896
   Summary: [internals] Represent string and arrays as sparse
literals
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: ibuc...@gdcproject.org

Given the following:
---
auto f = cast(char[2147483646]) "ab";
---

In the front-end, the initializer for this array consumes 2GB of memory
(multiplied by the number of times it is copied, I count two or three times).

StringExp {
  size = 2147483646;
  value = "ab\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...";
}

When really, you could get away with only 32 bytes, if the data structure were
smarter.

StringExp {
  size = 2147483646;
  values [
{
  index = 0;
  value = 97;
},
{
  index = 1;
  value = 98;
}
  ]
}

--


[Issue 19895] Floating point exception casting zero length array

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19895

--- Comment #1 from Yuxuan Shui  ---
Slightly reduced:

void fn() {
void[] a ;
auto b = cast(byte[0][]) a;
}

--


[Issue 19895] New: Floating point exception casting zero length array

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19895

  Issue ID: 19895
   Summary: Floating point exception casting zero length array
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: yshu...@gmail.com

https://run.dlang.io/is/J0XIcF

--


[Issue 1197] "static if" + enum.max/enum.min doesn't compile (D1 only)

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1197

RazvanN  changed:

   What|Removed |Added

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

--- Comment #8 from RazvanN  ---
As per Dconf AGM, all D1 that do not manifest in D2 bugs shall be closed.

--


[Issue 340] [Tracker] Forward reference bugs and other order-of-declaration issues

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=340
Issue 340 depends on issue 1197, which changed state.

Issue 1197 Summary: "static if" + enum.max/enum.min doesn't compile (D1 only)
https://issues.dlang.org/show_bug.cgi?id=1197

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WONTFIX

--


[Issue 277] Named mixin operator resolution

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=277

RazvanN  changed:

   What|Removed |Added

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

--- Comment #4 from RazvanN  ---
(In reply to Jason O'Brien from comment #3)
> thanks for the workaround Bruno, though I'm afraid that would still be
> subject to the problems with operator resolution in my comment :(  Works
> great if you've only got one mixin however :)
> 
> As far as it being an enhancement, I can see your judgement there.  But I
> would still think the second issue is a bug, as it's simply ignoring the
> mixin name, which doesn't seem to make much sense to me.

It is not ignoring the name; it is basically trying to do += on an object (the
named mixin) that has void type. The named mixin is like a gateway to select
the proper method, not an object on which operator overloading can be applied.
The name for the mixin has the purpose of being explicitly used when you want
to disambiguate, not to be used as an aggregate declaration; changing this may
lead to surprising behavior.

Closing as invalid.

--


[Issue 19894] Structs with disabled postblit is still not copyable after defining a copy constructor

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19894

RazvanN  changed:

   What|Removed |Added

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

--- Comment #1 from RazvanN  ---
Once a postblit is defined (even if it is marked @disable) all copy
constructors are ignored (in the sense that the compiler will not insert calls
to them; the copy constructors can still be called explicitly).

In this specific situation, disabling the postblit in a member field will make
the struct uncopyable, which is the correct behavior. If you want to make A
uncopyable but still, have Move(T) copyable, simply use only copy constructors:

struct Move(T) {
private:
import std.algorithm : move;
T storage;
public:
this(ref return scope Move rhs) {}
}

struct A {
@disable this(ref A);
}

void main() {
Move!A x;
Move!A y = x;
}

--


[Issue 827] Trying to break out of a labelled BlockStatement breaks out of a for loop at its beginning

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=827

RazvanN  changed:

   What|Removed |Added

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

--- Comment #5 from RazvanN  ---
The code in the original bug report now errors in D2. Closing as WORKSFORME.

--


[Issue 8622] Allow labeled breaks to work on *any* block

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8622
Issue 8622 depends on issue 827, which changed state.

Issue 827 Summary: Trying to break out of a labelled BlockStatement breaks out 
of a for loop at its beginning
https://issues.dlang.org/show_bug.cgi?id=827

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

--


[Issue 463] [module] private module members have global bindings instead of local ones

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=463

RazvanN  changed:

   What|Removed |Added

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

--- Comment #2 from RazvanN  ---
In D2, readelf now outputs WEAK for foo in all the examples in the original bug
report. WEAK is like global but the symbol can be overriden. Is there a
situation where this is a problem? If not, can we close this?

--


[Issue 19190] pragma(msg) changes the semantics of a program

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19190

Yuxuan Shui  changed:

   What|Removed |Added

Summary|Circular reference error|pragma(msg) changes the
   |resolved by getting |semantics of a program
   |allMembers  |

--


[Issue 19190] Circular reference error resolved by getting allMembers

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19190

--- Comment #5 from Yuxuan Shui  ---
This code even triggers an "Error: unknown":

https://run.dlang.io/is/ntQYrl

--


[Issue 19190] Circular reference error resolved by getting allMembers

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19190

Yuxuan Shui  changed:

   What|Removed |Added

   Severity|enhancement |normal

--- Comment #4 from Yuxuan Shui  ---
The behavior is changed since 2.069.2, as run.dlang.io shows:

https://run.dlang.io/is/lOtIDw

--


[Issue 19794] const on AliasSeq ignored

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19794

Yuxuan Shui  changed:

   What|Removed |Added

   Severity|normal  |enhancement

--


[Issue 19190] Circular reference error resolved by getting allMembers

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19190

--- Comment #3 from Yuxuan Shui  ---
The behavior is changed since 2.069.2, as run.dlang.io shows:

https://run.dlang.io/is/lOtIDw

--


[Issue 19794] const on AliasSeq ignored

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19794

Yuxuan Shui  changed:

   What|Removed |Added

   Severity|enhancement |normal

--


[Issue 19120] Cannot slice a struct with a tuple alias this

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19120

--- Comment #3 from Yuxuan Shui  ---
To clarify:

The problem of comment #0 is that Y is actually an array (A!(int, double)[0]).
So that is not a valid example.

But the problem is real, as the example in comment #2 shows. It is possible to
index A!(int, double), but not slicing it. Which seems to be an arbitrary
limitation.

--


[Issue 19120] Cannot slice a struct with a tuple alias this

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19120

Yuxuan Shui  changed:

   What|Removed |Added

 Status|REOPENED|NEW

--


[Issue 19469] File.byLine reuses buffer

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19469

Yuxuan Shui  changed:

   What|Removed |Added

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

--


[Issue 19891] Confusing error message for auto ref parameters with default values

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19891

Yuxuan Shui  changed:

   What|Removed |Added

   Severity|enhancement |normal

--


[Issue 19894] New: Structs with disabled postblit is still not copyable after defining a copy constructor

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19894

  Issue ID: 19894
   Summary: Structs with disabled postblit is still not copyable
after defining a copy constructor
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Severity: normal
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: yshu...@gmail.com

Example: https://run.dlang.io/is/BYs5vZ

--


[Issue 2396] -O causes very long execution time on foreach loop of large array of structs

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=2396

Mike Franklin  changed:

   What|Removed |Added

 CC||slavo5...@yahoo.com

--- Comment #13 from Mike Franklin  ---
Can this be closed?

--


[Issue 194] DDoc: method-attributes ignored within templated class

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=194

RazvanN  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #6 from RazvanN  ---
I cannot reproduce this on git HEAD ubuntu 16.04. Closing as WORKFSFORME.

--


[Issue 971] [profile] No profiling output is generated if the application terminates with exit

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=971

RazvanN  changed:

   What|Removed |Added

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

--- Comment #9 from RazvanN  ---
Tested on git HEAD master and trace.def/trace.log are both generated for both
files in the original bug report. Closing as WORKSFORME, please reopen if the
bug still manifests.

--


[Issue 13471] CTFE glitch when executing std.digest.crc.crc32Of() and checking the result with enforce(). (keyword: uninitialized variable)

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13471

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #3 from Dlang Bot  ---
dlang/phobos pull request #6976 "Fix issue 13471: can't use crc at CTFE" was
merged into master:

- 516432d185bf4ace339f7e571f1b46894e8536aa by Nicholas Lindsay Wilson:
  Fix issue 13471: can't use crc at CTFE

https://github.com/dlang/phobos/pull/6976

--


[Issue 17248] Multiple wrong function definitions in core.sys.windows.winldap (causing runtime issues)

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17248

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #2 from Dlang Bot  ---
dlang/druntime pull request #2603 "fix ldap bindings, fix issue 17248" was
merged into stable:

- c4e2f9fb7de19f5da9b8e6af462eacad39a01b91 by WebFreak001:
  fix ldap bindings, fix issue 17248
  Looked up and corrected most LDAP methods:
  changed char* (PCHAR) arguments to
  const(char)* (PCSTR) where documentation say const
  Renamed some types like in the documentation (purely aesthetic)
  Fixed a PLDAPControlW actually being PLDAPControlA in an ASCII method
  Changed [] arguments to * (fixed the referenced issue)

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

--


[Issue 13471] CTFE glitch when executing std.digest.crc.crc32Of() and checking the result with enforce(). (keyword: uninitialized variable)

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13471
Issue 13471 depends on issue 19892, which changed state.

Issue 19892 Summary: Add CTFE support for std.bitmanip: nativeToBigEndian, 
bigEndianToNative, littleEndianToNative, nativeToLittleEndian
https://issues.dlang.org/show_bug.cgi?id=19892

   What|Removed |Added

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

--


[Issue 19892] Add CTFE support for std.bitmanip: nativeToBigEndian, bigEndianToNative, littleEndianToNative, nativeToLittleEndian

2019-05-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19892

Dlang Bot  changed:

   What|Removed |Added

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

--- Comment #2 from Dlang Bot  ---
dlang/phobos pull request #7023 "Fix Issue 19892 - Add CTFE support for
std.bitmanip: nativeToBigEndian, bigEndianToNative, littleEndianToNative,
nativeToLittleEndian" was merged into master:

- 3578675d26062635794088c898bc65a521ba2ae6 by Nathan Sashihara:
  Fix Issue 19892 - Add CTFE support for std.bitmanip: nativeToBigEndian,
bigEndianToNative, littleEndianToNative, nativeToLittleEndian

https://github.com/dlang/phobos/pull/7023

--