[Issue 21884] [betterC] can't compare arrays with -betterC

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21884 Iain Buclaw changed: What|Removed |Added Priority|P1 |P3 --

[Issue 21884] [betterC] can't compare arrays with -betterC

2022-06-04 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21884 Walter Bright changed: What|Removed |Added Keywords||betterC CC|

[Issue 21884] [betterC] can't compare arrays with -betterC

2021-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21884 --- Comment #3 from Blatnik --- Here's a "fixed" version of core.internal.array.equality.__equals that acts correctly in betterC. I'm sure it could be done better but at least it works. bool __equals(T1, T2)(scope T1[] lhs, scope T2[] rhs) if (!__tr

[Issue 21884] [betterC] can't compare arrays with -betterC

2021-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21884 --- Comment #2 from Blatnik --- It also seems like the fixed size array comparisons (type[N] == type[N]) are implemented internally in DMD. However slice comparisons (type[N][] == type[N][]) are implemented in the runtime. The compiler converts flo

[Issue 21884] [betterC] can't compare arrays with -betterC

2021-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21884 --- Comment #1 from Blatnik --- It's also important to point out that fixing the first issue (type[N] == type[N]) would also fix the second issue. The only reason type[N][] == type[N][] doesn't work, is because it internally tries to compare every e