[Issue 15024] Wrong keyword color for Visual Studio Dark theme
https://issues.dlang.org/show_bug.cgi?id=15024 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Rainer Schuetze --- released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 14873] Build fails with message 'cannot create PDB file'
https://issues.dlang.org/show_bug.cgi?id=14873 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Rainer Schuetze --- released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 14524] Right clicking in solution explorer to add folders does not work as expected
https://issues.dlang.org/show_bug.cgi?id=14524 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Rainer Schuetze --- released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 14866] Unable to find universal runtime static libraries on windows 10 and VS 2015
https://issues.dlang.org/show_bug.cgi?id=14866 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Rainer Schuetze --- released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 15107] Win32-COFF library paths are blank
https://issues.dlang.org/show_bug.cgi?id=15107 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Rainer Schuetze --- released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 12021] VS2012-2013 .vcxproj files don't show in the solution explorer
https://issues.dlang.org/show_bug.cgi?id=12021 Rainer Schuetze changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Rainer Schuetze --- fixed in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 12128] C++ conversion error: not parsed until the end of the file
https://issues.dlang.org/show_bug.cgi?id=12128 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Rainer Schuetze --- https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 brings some improvements. The biggest one is that other messages are no longer suppressed when the C++ parser is confused and emits "not parsed until the end of the file". This allows to file more specific errors, so I'll close this one. --
[Issue 15345] Assembler highlighting done wrong
https://issues.dlang.org/show_bug.cgi?id=15345 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED CC||r.sagita...@gmx.de Resolution|--- |FIXED --- Comment #1 from Rainer Schuetze --- Thanks for reporting, fixed in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43 --
[Issue 14956] C++ Mangling incompatible with C++11
https://issues.dlang.org/show_bug.cgi?id=14956 --- Comment #7 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/574542fe2cf83dc32ce59fd82631184de91ef2a5 Merge pull request #5262 from ibuclaw/issue14956b [14965]: Add versioned-out branch to support new C++-11 implementations of std::string --
[Issue 11595] __traits(allMembers, packageName) behaves oddly.
https://issues.dlang.org/show_bug.cgi?id=11595
blm...@gmail.com changed:
What|Removed |Added
CC||blm...@gmail.com
--- Comment #2 from blm...@gmail.com ---
A more minimal test case:
---
module main;
import core.thread;
//Broken:
pragma(msg, __traits(allMembers, core));
//Seems to work:
pragma(msg, __traits(allMembers, core.thread));
void main() {}
---
The interesting thing is that the issue only seems to surface for root
packages. In the backend source, when working with __traits (see traits.d),
most package symbols have been resolved to Package objects, but root package
names haven't been fully resolved; they're still Import objects. That's
probably related to this issue.
--
[Issue 15369] [REG master] id.d(369): Error: Outside Unicode code space
https://issues.dlang.org/show_bug.cgi?id=15369 --- Comment #4 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/f13d425262073764f5389cc3717b4faf20c18058 fix Issue 15369 - id.d(369): Error: Outside Unicode code space https://github.com/D-Programming-Language/dmd/commit/7b2a4fff5d7ba3cb35a2d5341f62b48d6ce79df3 Merge pull request #5280 from 9rnsr/fix15369 [REG master] Issue 15369 - id.d(369): Error: Outside Unicode code space --
[Issue 15385] New: Apply Andersson91 idea to SortedRange.contains
https://issues.dlang.org/show_bug.cgi?id=15385 Issue ID: 15385 Summary: Apply Andersson91 idea to SortedRange.contains Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1 Component: phobos Assignee: nob...@puremagic.com Reporter: and...@erdani.com http://user.it.uu.se/~arnea/ps/searchproc.pdf describes a simple trick that reduces the number of comparisons in a binary search. The same idea can be used for binary search in an array. The idea is to save an index (not a node as described in the paper). In https://github.com/D-Programming-Language/phobos/blob/master/std/range/package.d#L7833 the routine could do only one evaluation of predFun and then continue searching. Only when the count goes down to zero is the other comparison done. --
[Issue 15352] template arguments matching error with delegates
https://issues.dlang.org/show_bug.cgi?id=15352 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/d8eb30c8da082cb7533a95c3930be46f818edadf fix Issue 15352 - template arguments matching error with delegates 1. `match()` function relies on `Expression.equals()`. Add `FuncExp.equals` for the identity comparison of two `FuncExp`s. 2. When a `FuncLiteralDeclaration` is listed directly in template arguments, it needs to be converted to `FuncExp` to be able to match `TemplateValueParameter`. https://github.com/D-Programming-Language/dmd/commit/a498e675b5a685494a2168a9438fe34b0467650a Merge pull request #5275 from 9rnsr/fix15352 Issue 15352 - template arguments matching error with delegates --
[Issue 13533] std.datetime should support custom parsing and formatting functions
https://issues.dlang.org/show_bug.cgi?id=13533 Chris Wright changed: What|Removed |Added CC||dhase...@gmail.com --
[Issue 12021] VS2012-2013 .vcxproj files don't show in the solution explorer
https://issues.dlang.org/show_bug.cgi?id=12021 --- Comment #8 from Manu --- Perfect timing! I just ran into this again about 1 hour ago... been trying to find a workaround since ;) --
[Issue 15386] New: std.format.formatValue usage hangs
https://issues.dlang.org/show_bug.cgi?id=15386
Issue ID: 15386
Summary: std.format.formatValue usage hangs
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P1
Component: phobos
Assignee: nob...@puremagic.com
Reporter: tachyon...@gmail.com
The set of 'internal' functions in std.format called "formatValue(...)" are not
private, so assuming users should be allowed to call them, consider the
following code:
import std.array, std.format;
auto w = appender!(Char[])();
auto fs = FormatSpec!Char("%.*s");
fs.writeUpToNextSpec(dor); // dor = DummyOutputRange that eats everything
formatValue(w, 0, fs);
The '*' in the format string means an additional argument would specify the
precision in this case. When calling std.format.format() or
std.format.formattedWrite() it will usually complain about 'expected int' or
'Range violation' which seems okay - at least it's better than what the code
above does, which appears to hang the program indefinitely.
If the above code is just bad usage and I should use the formattedWrite
interface, then should the other components of std.format be private?
On a similar note: is the format string happens to be compile-time constant, as
it is in this case, shouldn't it be possible to check the variadic arguments
against the string and find the error at compile time? I suppose it would
need to be a template parameter string.
--
[Issue 15386] std.format.formatValue usage hangs
https://issues.dlang.org/show_bug.cgi?id=15386 --- Comment #1 from Doug Nickerson --- Actually, letting it run longer reveals that it is not hanging but consuming over 4Gb of memory as it is generating a string of approx 2^32 '0's. lol. I think this is using the placeholder value defined in FormatSpec for a dynamically specified precision (or width) which is near int.max. Maybe this is the intended behavior in this (probably incorrect) use case, but it is concerning since format strings are runtime values that can change -- simply putting a '*' in there can allocate 4Gb of memory and/or cause an OutOfMemory error. --
[Issue 15281] std\experimental\allocator\package.d not included in build script
https://issues.dlang.org/show_bug.cgi?id=15281 monkeywork...@hotmail.com changed: What|Removed |Added CC||monkeywork...@hotmail.com --- Comment #4 from monkeywork...@hotmail.com --- https://github.com/D-Programming-Language/phobos/pull/3841 --
