[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 Manu changed: What|Removed |Added CC||turkey...@gmail.com --- Comment #3 from Manu --- Fin

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #4 from Walter Bright --- >From the "About Chrome" page: --- Google Chrome is up to date Version 85.0.4183.102 (Official Build) (64-bit) --- I'm running on 64 bit Win7. I've had zero issues before with anything on the dlang web site. -

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #5 from Walter Bright --- Created attachment 1804 --> https://issues.dlang.org/attachment.cgi?id=1804&action=edit Chrome's rendering of the changlog A picture is worth 1000 words. --

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #6 from Walter Bright --- Scrolling up and down creates completely erratic rendering. --

[Issue 3713] Tail call optimization not enabled with the ?: operator

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3713 --- Comment #4 from Dlang Bot --- @WalterBright created dlang/dmd pull request #11725 "fix Issue 3713 - Tail call optimization not enabled with the ?: operator" fixing this issue: - fix Issue 3713 - Tail call optimization not enabled with the ?: oper

[Issue 3713] Tail call optimization not enabled with the ?: operator

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3713 Walter Bright changed: What|Removed |Added Keywords||performance --

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 Ethan Watson changed: What|Removed |Added CC||goober...@gmail.com --- Comment #7 from Ethan

[Issue 21242] New: is expression documentation lacks module

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21242 Issue ID: 21242 Summary: is expression documentation lacks module Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: minor Priority: P

[Issue 3713] Tail call optimization not enabled with the ?: operator

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3713 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 21243] New: Allow lambdas to return auto ref

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21243 Issue ID: 21243 Summary: Allow lambdas to return auto ref Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priority

[Issue 20908] -preview=nosharedaccess requires zero-initializion for aggregates

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20908 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @Geod24

[Issue 20195] -preview=nosharedaccess has some access problems

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20195 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #7 from Dlang Bot --- @Geod24

[Issue 8929] long.min is a Voldemort literal

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8929 Mathias LANG changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #8 from Walter Bright --- (In reply to Ethan Watson from comment #7) > Either way, this is clearly a user-support issue for Chrome and not a fault > with the document itself. I've never seen this behavior before. It does not happen with

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #9 from Ethan Watson --- (In reply to Walter Bright from comment #8) > I've never seen this behavior before. I have. I said that I have. I have personally seen exactly the behavior you screenshotted on my computer. Years ago, because of

[Issue 21244] New: Error: expression `hasToString!(..., char)` of type `void` does not have a boolean value

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21244 Issue ID: 21244 Summary: Error: expression `hasToString!(..., char)` of type `void` does not have a boolean value Product: D Version: D2 Hardware: All OS: All

[Issue 21245] New: Error: expression `canBitwiseHash!(...)` of type `void` does not have a boolean value

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21245 Issue ID: 21245 Summary: Error: expression `canBitwiseHash!(...)` of type `void` does not have a boolean value Product: D Version: D2 Hardware: All OS: All

[Issue 21246] New: Compiler must show mismatching types when functions do not properly override

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21246 Issue ID: 21246 Summary: Compiler must show mismatching types when functions do not properly override Product: D Version: D2 Hardware: All OS: All Sta

[Issue 21241] html display of changelog does not work in Chrome browser

2020-09-13 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21241 --- Comment #10 from Walter Bright --- (In reply to Ethan Watson from comment #9) > Disable all your extensions and try again. Turn off GPU rendering and try > again. Something in there is broken, not the page. I understand that. My point isn't that