liftResourceT (#61)
Add foldMap sink
Add simple tests for foldMap
Merge pull request #66 from alphaHeavy/foldMap

Add foldMap sink
Better transPipe docs (#67)
Add UDP message source and sink
Factor out getPort and bindPort into a new module

This will allow for exporting the same actions using UDP without code
duplication.
Add getSocket and bindPort actions to UDP support
Add udpflow sample application

This is a very simple application which forks 2 threads, one sending
messages to a port, another one receiving (and discarding) them.

The application should be built using the threaded RTS. Consider using
2 capabilities upon execution (+RTS -N2).
Add Data.Conduit.List.iterM

This Conduit simplifies performing a monadic action for every value
generated by a Source, and passing the value on as-is.
Add QuickCheck tests for iterM behaviour and mapM equivalence

Requested in pull-request review.

See: https://github.com/snoyberg/conduit/pull/68#issuecomment-8113128
Add finalizers to udpflow example

Yet, according to strace, they don't seem to work...
Rework sinkSocket

This commit reworks sinkSocket into 4 versions, introducing support for
connected and disconnected sockets (sinkSocket & sinkAllSocket vs.
sinkToSocket & sinkAllToSocket) as well as send-style and sendAll-style
message processing (sinkSocket & sinkToSocket vs. sinkAllSocket &
sinkAllToSocket).

This breaks the former sinkSocket API.
Rework udpflow sample to use a connected socket
Inline D.C.N.UDP.sinkSocketHelper

As requested by Felipe @meteficha Lessa in the pull-request review.
Checking GHC Core indicates no automatic inlining is performed, so the
pragma makes perfect sense.

See: https://github.com/NicolasT/conduit/commit/68fba0df5fdaf1a7200caa1ff35e4a89ce9ad59c#network-conduit-data-conduit-network-udp-hs-P79
Fix resource handling in udpflow sample

Thanks to comments by Felipe @meteficha Lessa in the pull-request
review. Now strace does show the expected close calls.

See: https://github.com/snoyberg/conduit/pull/69#commitcomment-1781636
Add Message structure and yield it

This commit introduces a Message data type which is used as a
representation of UDP messages, which are yielded by the UDP source
instead of the somewhat less appropriate tuples as before.

Discussed in the pull-request review.

See: https://github.com/snoyberg/conduit/pull/69#issuecomment-8160779
Use Message for sink*ToSocket

For consistency with sourceSocket, the signature of sink*ToSocket sinks
is changed to use the Message type, instead of tuples.

See: https://github.com/snoyberg/conduit/pull/69#issuecomment-8171595
Remove UDP message payload zero-length check

Zero-length payload UDP messages might be allowed at the protocol
layer, yet it looks like the low-level actions throw an EOFError
when a zero-length message is encountered.

Removing the check is safe and ensures compatibility with the behaviour
of the underlying action.

See: https://github.com/snoyberg/conduit/pull/69#commitcomment-1781596
See: http://hackage.haskell.org/packages/archive/network/2.3.1.0/doc/html/src/Network-Socket.html#recvBufFrom
Merge pull request #69 from NicolasT/udp-support

Add UDP support