[Issue 17363] @safety hole due to $ caching in slice expressions

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

[Issue 17363] @safety hole due to $ caching in slice expressions

https://issues.dlang.org/show_bug.cgi?id=17363 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #4 from

[Issue 17363] @safety hole due to $ caching in slice expressions

https://issues.dlang.org/show_bug.cgi?id=17363 --- Comment #3 from anonymous4 --- Because you can't resolve $ before loading the array, therefore loading before resolution is the only way to do it. --

[Issue 17363] @safety hole due to $ caching in slice expressions

https://issues.dlang.org/show_bug.cgi?id=17363 --- Comment #2 from ki...@gmx.net --- > The slice should be loaded before evaluation of slice arguments, then length > is safe to cache, see issue 17364. Your argument for loading & caching length and pointer before evaluating the bounds expressions

[Issue 17363] @safety hole due to $ caching in slice expressions

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

[Issue 17363] @safety hole due to $ caching in slice expressions

https://issues.dlang.org/show_bug.cgi?id=17363 anonymous4 changed: What|Removed |Added Keywords||safe --