News for hackers. Stuff that matters.

A comment on Measuring GC latencies in Haskell, OCaml, Racket. Parent comment

Re:Measuring GC latencies in Haskell, OCaml, Racket by marcosdumay on Monday December 05, 2016 @08:12AM (#13105095)
That's what you get by importing qualified and being too verbose.

This same can be written as:

  type Chan = Map Int ByteString
People do prefer importing Map and ByteString qualified, so their functions will have a prefix of their choice. But very few people import ByteString as "ByteString", most use something shorter.
[ Parent | on HN ]
Re:Measuring GC latencies in Haskell, OCaml, Racket by moomin on Monday December 05, 2016 @09:16AM (#13105433)
Gotta say, I'm Team Qualified Import. Use it all the time in my Clojure code. I want to know where things come from.
[ Parent | on HN ]
Re:Measuring GC latencies in Haskell, OCaml, Racket by marcosdumay on Monday December 05, 2016 @10:43AM (#13106092)
On Haskell you don't even get much choice. The community is so biased towards qualified importing that most modules clash, and you'd need some incredible stretching to use them unqualified.

As most things in Haskell, it tends to work greatly. The usual problems go away due to some combination of Haskell's features and the main problems are things you wouldn't think about.

[ Parent | on HN ]
Re:Measuring GC latencies in Haskell, OCaml, Racket by hood_syntax on Monday December 05, 2016 @10:11AM (#13105767)
Totally reasonable, but most people would use BS instead of ByteString as the qualified name.
[ Parent | on HN ]