It's not the best idea to always unconditionally use .array because you might wa... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

jordigh on Oct 15, 2019 | parent | context | favorite | on: My Vision of D’s Future

It's not the best idea to always unconditionally use .array because you might want to preserve the laziness of a Result type. By using .array you're saying you want all of the results into memory right now! Depending on what you're doing, you might not want that.

abaga129 on Oct 15, 2019 [–]

I actually didn't know this! Very cool. I guess it's similar to calling .ToList() on IEnumerable<T> in C#.

p0nce on Oct 16, 2019 | [–]

Most range function return a "Voldemort" that preserve lazyness if you put it in an `auto` local. Or you can use .array to get a slice out of it.

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact