Conversation

I qualify and/or make explicit all my imports in Haskell today because of my limited time in Purescript. The code is easier for people new to the codebase to pick up what is going on too. Thanks #purescript! :)

Quote Tweet

harry

@hdgarrood

· Sep 17, 2019

Replying to @rob_rix @jfischoff and @sclv

Pretty much everyone does in purescript land, but that’s because the compiler warns about open imports by default

Brendan Zabarauskas

@brendanzab

Replying to

@SusanPotter

As someone who reads much more Haskell than I ever write, I can concur that explicit imports are most appreciated pretty much all the time!

10:07 AM · Sep 18, 2019Twitter for iPhone

Replying to

The secret (typically, unless you write and forget/not-maintain code) is authors/maintainers read the codebase more of the time than they actually write too. I might be selfish and have a puny working memory. :)

Brendan Zabarauskas

@brendanzab

Sep 18, 2019

Perhaps I’m in the weird position where I read lots of code from different languages for guidance and inspiration, most of it unfamiliar. The biggest time sink is tracking down where something comes from. Hopefully GitHub’s semantic helps, but it wont solve it for Gitlab etc.

Replying to

and

Haskell isn’t the only one though - Agda, Coq, Lean, OCaml, etc. also can be quite frustrating to read if the author isn’t disciplined with explicit imports. Hopefully better code navigation tools come to our aid here, but in the interim it can be rather a pain. 😔