Tyson Williams

> > I would also like the function arguments in all the Binding methods to be fully curried (as I mentioned in [#266 (comment)](https://github.com/elmish/Elmish.WPF/pull/266#discussion_r472307305)). I think think of two advantages...

>> ...The second is because DU case constructors are uncurried functions.... > > The reason for `toMsg` being the way it is, is because typically the DU constructor case for...

> Regarding `toBindingModel`, I can't remember why it was like that in the first place. Perhaps it was just some internal design that leaked out into the signature without my...

> > Regarding `toBindingModel`, I can't remember why it was like that in the first place. Perhaps it was just some internal design that leaked out into the signature without...

Thanks for pointing out those examples. I suppose I could have found them if I had looked harder. I guess I am fine with the status quo.

> I would be satisfied if we published a NuGet package from our our `v4` branch at various points as a pre-release. Something like `Elmish.WPF 4.0-beta.1`. It would be useful...

> Any strong opinions on alpha vs. beta? None at all. > Prerelease version format on NuGet (and in the `fsproj`) is `4.0.0-alpha-1`. If you think there's a chance there'll...

Almost worked. Quoting the [build logs when I pushed the tag](https://ci.appveyor.com/project/cmeeren/elmish-wpf/builds/34764408). > "NuGet" deployment has been skipped as environment variable has not matched ("appveyor_repo_tag" is "false", should be "true")

Actually, I don't need this on nuget.org. I just remembered that we have a folder as a NuGet package source for some other NuGet packages for conveniences just like this....

Oh, now I see that the tag I created only exists locally. That explains it. I will still go with the local approach unless someone else requests a prerelease.