[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 --- Comment #4 from basile-z --- As of v 2.108 DMD is consistent and always verifies that the slice is equal to `[1]`. Maybe that now the issue could be closed with a PR introducing a test with `version()` for each compiler ? --

[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 Iain Buclaw changed: What|Removed |Added Priority|P1 |P3 --

[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 anonymous4 changed: What|Removed |Added See Also|

[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 --- Comment #3 from anonymous4 --- (In reply to kinke from comment #2) > but *when* the loads happen is clearly crucial That's the loading I talk about. --

[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 --- Comment #2 from ki...@gmx.net --- > For example you can't resolve length before loading the array. Not sure what you mean by 'loading the array'. The base expression evaluates to a slice, a pointer+length pair, in these 2 cases either to a

[Issue 17364] Difference between slicing a slice and a reference to a slice

https://issues.dlang.org/show_bug.cgi?id=17364 anonymous4 changed: What|Removed |Added Keywords||spec --- Comment #1