[Issue 14533] Error 43: Not a Valid Library File

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14533 --- Comment #2 from donglei do...@putao.com --- (In reply to Richard Cattermole from comment #1) Just to confirm this is for 64bit builds on Windows? And not the default of 32bit? Windows system is 64bit, but dmd is 32bit! It maybe cased by COFF

[Issue 14533] Error 43: Not a Valid Library File

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14533 --- Comment #3 from Richard Cattermole alphaglosi...@gmail.com --- (In reply to donglei from comment #2) (In reply to Richard Cattermole from comment #1) Just to confirm this is for 64bit builds on Windows? And not the default of 32bit?

[Issue 14543] New: std.algorithm.searching.until does not handle range sentinels nicely

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14543 Issue ID: 14543 Summary: std.algorithm.searching.until does not handle range sentinels nicely Product: D Version: D2 Hardware: All OS: All Status:

[Issue 14508] [REG2.067.0] compiling with -unittest instantiates templates in non-root modules

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14508 Martin Krejcirik m...@krej.cz changed: What|Removed |Added Summary|compiling with -unittest|[REG2.067.0] compiling with

[Issue 14544] New: isForwardRange failed to recognise valid forward range

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14544 Issue ID: 14544 Summary: isForwardRange failed to recognise valid forward range Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal

[Issue 14534] Front-end should lower all non-scalar condition expressions

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14534 Iain Buclaw ibuc...@gdcproject.org changed: What|Removed |Added CC||ibuc...@gdcproject.org

[Issue 14534] Front-end should lower all non-scalar condition expressions

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14534 --- Comment #4 from yebblies yebbl...@gmail.com --- (In reply to Iain Buclaw from comment #3) In some cases, yes. But in this instance, I don't think so. After we've verified condition-toBoolean() the only other time semantic analysis is done

[Issue 14544] isForwardRange failed to recognise valid forward range

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14544 Jonathan M Davis issues.dl...@jmdavisprog.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 14544] isForwardRange failed to recognise valid forward range

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14544 --- Comment #2 from Ketmar Dark ket...@ketmar.no-ip.org --- wow, it's fun. it specified nowhere in the docs. what i see is with the save primitive, which clearly not necessary a property. it also contradics my common sense too. with the fix i

[Issue 14545] New: can't deprecate default construction

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14545 Issue ID: 14545 Summary: can't deprecate default construction Product: D Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 14544] isForwardRange failed to recognise valid forward range

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14544 --- Comment #3 from Jonathan M Davis issues.dl...@jmdavisprog.com --- Oh, it's stupid that save is required to be a property, since it's not at all an abstraction for a variable, but I don't think that Andrei really understands the idea behind

[Issue 14544] isForwardRange failed to recognise valid forward range

2015-05-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14544 --- Comment #4 from Ketmar Dark ket...@ketmar.no-ip.org --- something should be fixed, i think. either documentation, or `isForwardRange`. and fixing `isForwardRange` will not break anything, as it will happily accept both prop and non-prop `save`...