Lazy vs Strict ByteStrings

15 Mar
2017
15 Mar
'17
1:12 a.m.
I just noticed that I avoid using ByteStrings because I tend to spend a huge amount of time reading GHC output and trying to figure out if I am/should be using the strict or the lazy version. I have to use both lazy/strict because different libraries use different versions. Maybe having different names would have helped. Am I doing something wrong or is the interface to ByteStrings a poor design? Cheers, Dimitri -- 2E45 D376 A744 C671 5100 A261 210B 8461 0FB0 CA1F
2988
Age (days ago)
2988
Last active (days ago)
0 comments
1 participants
participants (1)
-
Dimitri DeFigueiredo