removed dependency on bytestring-conversion #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I'm suggesting the elimination of the dependency on
bytestring-conversion
, by replacing the use ofData.ByteString.Conversion.toByteString'
withData.Text.Encoding.encodeUtf8
, and usingencodeUtf8
directly in the ToHttpApiData Link and [Link] implementations, given thatwriteLinkHeader
andwriteLink
return Text, andData.ByteString.Conversion.toByteString'
appears to resolve to a call toencodeUtf8 :: Text -> ByteString
for Text. This allows the elimination of theToByteString
implementations forLink
and[Link]
, which so far as I can tell are for internal use only.The dependency on
bytestring-conversion
happens to be causing a build problem forstack --docker
with LTS-13.1. This fix solves that. The dependency on text exists already.results of stack test suggest no problems:
thanks,
Stephen.