OverloadedString in source code #194
Labels
No Label
blocked: dependency
blocked: info-needed
bug
duplicate
enhancement
fixed in HEAD
help wanted
hs:arrows
hs:brackets
hs:classes
hs:comments
hs:do-notation
hs:guards
hs:lists
hs:operators
hs:patterns
hs:records
hs:types
invalid
language extension support
layouting
needs confirmation
priority: high
priority: low
question
revisit before next release
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: hexagoxel/brittany#194
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Right now the pattern
docLit $ Text.pack "Some string"
is all over the layouting functions. If we enableOverloadedStrings
those can all be reduced todocLit "Some string"
, which would aid readability for complex layouts.@lspitzner is there a specific reason not to use
OverloadedStrings
or did you just not choose to. Do you think it makes sense to enable it in a few files?I can't speak for Lennart, but I sometimes avoid
OverloadedStrings
because I'm not comfortable with howByteString
s behave. That being said, it's usually worth the convenience to me.