News for hackers. Stuff that matters.
Re:Big Programming, Small Programming – Glow, the language by gjm11 on Tuesday September 17, 2013 @07:05AM (#6398584)
Unless you're happy giving all your imports single-letter names (why hello, BASIC circa 1970!) it's more like: foo.bar in Python, OtherModule.bar foo in Haskell. That does seem like quite a lot more typing.
Re:Big Programming, Small Programming – Glow, the language by pestaa on Tuesday September 17, 2013 @08:25AM (#6398837)
I usually see Data.Map to imported as M, Text.ByteString as BS, etc. If you need more than a couple of these, I'd say it is a red flag and that the code needs to be split up.
Re:Big Programming, Small Programming – Glow, the language by mercurial on Tuesday September 17, 2013 @09:12AM (#6399049)
It's in my experience much easier to avoid accidental namespace clashes with functions than with accessors (though some modules are intended to be imported qualified). If you need to model a real-world problem, you run into record namespace clashes very easily.