[Issue 1998] std.bitarray should have setAll / opSliceAssign(bool) etc

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1998 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--

[Issue 4717] std.bitmanip.BitArray changes

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4717 --- Comment #11 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/7a3700135944be30279aeaec0aa32849fdc30adc Fix Issue 4717 - std.bitmanip.BitArray changes --

[Issue 1998] std.bitarray should have setAll / opSliceAssign(bool) etc

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1998 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/24080dfe95d9cb1fea86511e80c467be68bb7946 Fix Issue 1998 - std.bitarray should have setAll / opSlic

[Issue 4717] std.bitmanip.BitArray changes

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4717 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--

[Issue 17928] [scope] `in` is not treated as `const scope`

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17928 --- Comment #3 from anonymous4 --- (In reply to Jonathan M Davis from comment #2) > Personally, I think that it was a mistake to create a storage class which > was equivalent to two other storage classes, but clearly, a number of folks > like the ide

[Issue 17914] [Reg 2.075] Fibers guard page uses a lot more memory mappings

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17914 --- Comment #10 from anonymous4 --- Judging by the code Generator can just destroy itself on termination. It's not reusable, is it? --

[Issue 15136] If we want toStringz to be fully correct, it needs to stop checking for '\0'

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15136 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment #3 fr

[Issue 16542] makeArray not usable with const initializer

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16542 github-bugzi...@puremagic.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|-

[Issue 16542] makeArray not usable with const initializer

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16542 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/cd66c0cba650d63785ccb79a115964e6472692ca fix issue 16542 https://github.com/dlang/phobos/commit/

[Issue 15136] If we want toStringz to be fully correct, it needs to stop checking for '\0'

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15136 --- Comment #4 from Steven Schveighoffer --- (In reply to Steven Schveighoffer from comment #3) > assert(s[5] == 'b'); That should have read str[5], obviously :) --

[Issue 5074] array(immutable(int)[]) ==> int[]

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5074 Andrei Alexandrescu changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Issue 12282] Immutable result of std.array.array

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12282 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 5351] Add template mixin for Range Primitives using random access

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5351 Eduard Staniloiu changed: What|Removed |Added Keywords||bootcamp CC|

[Issue 17742] std.range.transposed does not have opIndex

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17742 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment #1 fr

[Issue 17742] std.range.transposed does not have opIndex

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17742 --- Comment #2 from Vladimir Panteleev --- Ouch. I didn't realize transposed works with jagged arrays. Considering this issue and that transposed doesn't work with static arrays (because they're not ranges), maybe a separate function would be better

[Issue 17952] New: std.range.transposed save is invalid

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17952 Issue ID: 17952 Summary: std.range.transposed save is invalid Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: enhancement Prio

[Issue 13041] std.range.transposed consumes sub-ranges

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13041 Steven Schveighoffer changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 17607] not an associative array initializer

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17607 John Colvin changed: What|Removed |Added CC||john.loughran.colvin@gmail.

[Issue 17256] Inconsistent output between json and ddoc

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17256 --- Comment #1 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/608b82452befcd6463106b68e6c1b3e40887597c fix Issue 17256 - Inconsistent output between json and ddoc JS

[Issue 17256] Inconsistent output between json and ddoc

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17256 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Issue 17952] std.range.transposed save is invalid

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17952 --- Comment #1 from Steven Schveighoffer --- Scratch that, x is not really [[2,5],[3,6]], it's an empty range! Just using equals destroys it. transposed clearly isn't even close to a forward range. --

[Issue 17952] std.range.transposed save is invalid

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17952 --- Comment #2 from Steven Schveighoffer --- To ensure this test case is checking the right issue, change the third line to: assert(y.equal([[1,4],[2,5],[3,6]])); And get rid of the y.popFront. Clearly, we should be able to iterate y without itera

[Issue 17952] std.range.transposed save is invalid

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17952 Alexandru Razvan Caciulescu changed: What|Removed |Added CC||alexandru.razva...@gmail.co

[Issue 17851] htonl already defined in phobos64.lib

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17851 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/cf8ed256f956f1fb551c314881922b8fc817246b core.sys.windows.winsock2: Don't implement htons() et

[Issue 5351] Add template mixin for Range Primitives using random access

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5351 Simen Kjaeraas changed: What|Removed |Added CC||simen.kja...@gmail.com --- Comment #3 from S

[Issue 17953] New: inout-like mechanism to infer function attributes from callback attributes

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17953 Issue ID: 17953 Summary: inout-like mechanism to infer function attributes from callback attributes Product: D Version: D2 Hardware: Other OS: Other S

[Issue 17944] MSCOFF: debug info not compatible with LLVMs LLD

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17944 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/d75aaa258f155bd98004e8658e8921b7dba8bd51 fix issue 17944: MSCOFF: do not write empty debug$S section h

[Issue 17954] New: init member should be disallowed

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17954 Issue ID: 17954 Summary: init member should be disallowed Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1