Daniel Little

1. Would this move to using side effects instead? 2. Awesome, this has always bugged me, I think I commented it on it before 3. I've started doing something similar...

@Horusiath With regards to composing `actor` I'm taking about calling Receive once in a nested fashion. ``` let receivePreProcess mailbox = actor { let! msg = mailbox.Receive() match msg with...

I could fix this but I wanted to confirm that it would add a schedule for every at-least-once-delivery actor.

I've seen a lot of resistance in the past adding external dependencies to message contract libraries. Would this also require messages to be mutable? Or more than a simple record?

I've also run into an issue with the Wire constraint when installing via NuGet

We've been using a custom serialiser for unions which formats based on the shape. It's worked really well for us and we use it to send data to the client...

We also have a converter for Options which works like this: ``` Some "thing" -> "thing" None -> null ``` It's worked fairly well, but there is one problem, it's...

I'm very much in favour of the point @CarstenKoenig made which is object |> serialize |> deserialize should be lossless. I think one of the most common examples is interop...

@smoothdeveloper my initial interest for this change is that `Microsoft.Data.SqlClient` appears to have better support for dotnetcore, in particular this was the issue that got me thinking about it https://github.com/fsprojects/FSharp.Data.SqlClient/issues/373....

@smoothdeveloper I would assume so, but you would probably need two separate proj files as the dependencies would differ. They could both reference the same code and sit side by...