[Issue 22729] ICE: Invalid array access for invalid interface definition

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22729 moonlightsenti...@disroot.org changed: What|Removed |Added Hardware|x86_64 |All Summary|dmd cr

[Issue 22729] dmd crushed and asked to report a bug

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22729 --- Comment #11 from moonlightsenti...@disroot.org --- (In reply to Alexey from comment #5) > runned it like this: `dustmite . 'dub build' > ../dust_log 2>&1` Dustmite expects a command that exits with code 0 iff the error is present in the current

[Issue 22729] dmd crushed and asked to report a bug

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22729 moonlightsenti...@disroot.org changed: What|Removed |Added CC||moonlightsentinel@disroot.o

[Issue 22729] dmd crushed and asked to report a bug

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22729 --- Comment #9 from Alexey --- dustmite - doesn't helps --

[Issue 22729] dmd crushed and asked to report a bug

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22729 --- Comment #8 from Alexey --- got same bug again. I think this is about some mixture of interface recursion and mixins. still couldn't triangulate the problem, but it disappears if I comment out ': ContainerFunctionSetI' text in source/dtk/interfac

[Issue 22801] [REG 2.099.0-beta.1] Can't return address of return ref parameter from constructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22801 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 22801] [REG 2.099.0-beta.1] Can't return address of return ref parameter from constructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22801 --- Comment #3 from Dlang Bot --- @dkorpel created dlang/dmd pull request #13940 "Fix Issue 22801 - [master] Can't return address of return ref parameter from constructor" fixing this issue: - Fix Issue 22801 - Can't return address of return ref par

[Issue 22966] Inconsistent `shared` attribute for generated destructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22966 --- Comment #2 from kinke --- One more WTF: ``` struct WithDtor { int x; ~this() {} } struct A { WithDtor withDtor; } pragma(msg, A.__xdtor.mangleof); struct B { shared A a; } void main() { pragma(msg, A.__xdtor.mangleof); }

[Issue 22966] Inconsistent `shared` attribute for generated destructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22966 kinke changed: What|Removed |Added Keywords||industry --

[Issue 22966] Inconsistent `shared` attribute for generated destructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22966 --- Comment #1 from kinke --- Trying to work around this with an explicit dummy ctor does NOT work: ``` struct WithDtor { int x; ~this() {} } struct A { WithDtor withDtor; ~this() shared {} } struct B { version (Shared)

[Issue 22966] Inconsistent `shared` attribute for generated destructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22966 kinke changed: What|Removed |Added Summary|Inconsistent|Inconsistent `shared` |`shared`att

[Issue 22966] New: Inconsistent `shared`attribute for generated destructor

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22966 Issue ID: 22966 Summary: Inconsistent `shared`attribute for generated destructor Product: D Version: D2 Hardware: All OS: All Status: NEW Se

[Issue 22939] bad error message: Error: no property `msg` for type `string`

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22939 --- Comment #4 from Dlang Bot --- dlang/phobos pull request #8425 "merge stable" was merged into master: - ba92563a0d69d07f182ea7305bb6def1791a7bd8 by Dennis Korpel: Fix issue 22939 - bad error message: Error: no property `msg` for type `string`

[Issue 22908] OpenBSD: Add getpwnam_shadow and getpwuid_shadow function prototypes

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22908 --- Comment #3 from Dlang Bot --- dlang/druntime pull request #3793 "merge stable" was merged into master: - 2f2a68e2de870fd15ddcf45e37f18d7c941957e6 by Brian Callahan: Add core.sys.openbsd.pwd module. Fix Issue 22908 - OpenBSD: Add getpwnam_sha

[Issue 20778] exception messages with nulls within are treated inconsistently

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20778 --- Comment #2 from Dlang Bot --- dlang/druntime pull request #3793 "merge stable" was merged into master: - 84e429a7c7c99ebae6e72de2f2be3069266394a5 by MoonlightSentinel: Fix 20778 - Ensure that _d_print_throwable prints the entire message Th

[Issue 21086] Wrong source link for core.thread.context

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21086 --- Comment #4 from Dlang Bot --- dlang/druntime pull request #3793 "merge stable" was merged into master: - b87d7df8bf3244d772421008416263bab123e27e by MoonlightSentinel: Fix 21086 - Correct link core.thread.context The file is named `context.

[Issue 22221] [dip1000] pure function can escape parameters through Exception

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 20717] Unsilenced bogus "undefined identifier" error from speculative collision

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20717 --- Comment #9 from Dlang Bot --- dlang/dmd pull request #13937 "merge stable" was merged into master: - 7d6cc698eba28962d098f4c527d9e1a5371b0a19 by RazvanN7: Fix Issue 20717 - Unsilenced bogus undefined identifier error from speculative collision

[Issue 22965] New: assocArray does not automatically select non-immutable types even if they're easily reachable.

2022-04-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=22965 Issue ID: 22965 Summary: assocArray does not automatically select non-immutable types even if they're easily reachable. Product: D Version: D2 Hardware: x86_64 OS