[Issue 1308] Recursive alias declaration, Error: forward reference to foo

https://issues.dlang.org/show_bug.cgi?id=1308 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 1324] __FILE__ in mixin template expand to the definition, not the instantiation

https://issues.dlang.org/show_bug.cgi?id=1324 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #3 from Dlang Bot ---

[Issue 1479] mixin error across two module

https://issues.dlang.org/show_bug.cgi?id=1479 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 --- Comment #2 from Walter Bright --- For the moment, until I fix it, you can use db to insert the exact bytes you need. --

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 --- Comment #1 from Walter Bright --- Minimal test case: bool test() { asm { naked; cmpxchg [RDX], DIL; } } --

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 Walter Bright changed: What|Removed |Added Keywords||iasm --

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com

[Issue 20131] New: Bad codegen from inline asm; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 Issue ID: 20131 Summary: Bad codegen from inline asm; possible REX prefix missing Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 20116] Wrong delegate type when taking address of inout member function

https://issues.dlang.org/show_bug.cgi?id=20116 Simen Kjaeraas changed: What|Removed |Added CC||simen.kja...@gmail.com

[Issue 20132] New: segfault on fiber.call() in release mode

https://issues.dlang.org/show_bug.cgi?id=20132 Issue ID: 20132 Summary: segfault on fiber.call() in release mode Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal

[Issue 20134] New: autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 Issue ID: 20134 Summary: autodecode should use replacementDchar rather than throwing on invalid Product: D Version: D2 Hardware: All OS: All Status:

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 Walter Bright changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 14519] Get rid of unicode validation in string processing

https://issues.dlang.org/show_bug.cgi?id=14519 Walter Bright changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 --- Comment #4 from Vladimir Panteleev --- (In reply to Walter Bright from comment #1) > Over time, common practice has evolved from rejecting malformed UTF to > replacing it with replacementDchar, which enables the application (like a > web

[Issue 20116] Wrong delegate type when taking address of inout member function

https://issues.dlang.org/show_bug.cgi?id=20116 --- Comment #3 from Harry Vennik --- That is an interesting approach. Looks like that would fix this particular issue. But could you please elaborate on the effects of such semantic in the different, but related, case of Issue 15651? --

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #2 from Dlang Bot ---

[Issue 20133] New: [REG2.084.0] Bogus slice assignment in recursive CTFE call

https://issues.dlang.org/show_bug.cgi?id=20133 Issue ID: 20133 Summary: [REG2.084.0] Bogus slice assignment in recursive CTFE call Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 --- Comment #1 from Walter Bright --- Over time, common practice has evolved from rejecting malformed UTF to replacing it with replacementDchar, which enables the application (like a web browser) to continue processing. Code should also be faster

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 Vladimir Panteleev changed: What|Removed |Added CC||dlang-bugzilla@thecybershad

[Issue 20131] Bad codegen from inline asm LOCK CMPXCHG; possible REX prefix missing

https://issues.dlang.org/show_bug.cgi?id=20131 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 20134] autodecode should use replacementDchar rather than throwing on invalid

https://issues.dlang.org/show_bug.cgi?id=20134 Jon Degenhardt changed: What|Removed |Added CC||jrdemail2000-dl...@yahoo.co

[Issue 20113] Cannot find source code for runtime library file 'object.d' when the path contains '~'

https://issues.dlang.org/show_bug.cgi?id=20113 --- Comment #3 from Dlang Bot --- dlang/dmd pull request #10309 "[dmd-cxx] fix Issue 20113 - Cannot find source code for runtime library file 'object.d' when the path contains '~'" was merged into dmd-cxx: - 1e44c0ba6161ccc9074b45306abf5aabbeedd6be