I always interpreted the warning in the documentation as "Don't use the name LazyListView or the Nil and Cons constructors, instead using head, tail and headAndTail for most pattern matchng". I think it makes sense not to use the internal representation given that Dict and Array change when better implementations arise. Does any code elm code actually pattern match these instead of using the functions? Always thought it was weird to have this type exposed at all.
On Friday, November 10, 2017 at 8:58:33 AM UTC-8, Rupert Smith wrote: > > On Friday, November 10, 2017 at 4:45:54 PM UTC, Rupert Smith wrote: >> >> The function uses the exposed Lazy.List.LazyListView type, which I would >> rather avoid if it makes sense to: >> > > The documentation says: > > "It is not recommended to work with this type directly. Try working solely > with the provided functions in the package." > > But I wonder, does this really make sense? Its not like this library is > going to swap out that representation for another one at a later time is > it? In which case exposing the type and working with it directly, which is > needed for pattern matching anyway, is no different than working with say > the List type directly. > > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
