Order of msg mapping inputs

[TysonMN]

The parameter order in the set parameter of Binding.twoWay differs from the parameter order of the function accepted by Binding.mapMsgWithModel.

IIRC, one advantage of the order within Binding.mapMsgWithModel is that it matches what would be needed for that function to be the bind function if Binding<'model, 'msg> were a monad in 'msg (like how 'a -> 'b is a monad in 'b).

[TysonMN]

IIRC, one advantage of the order within Binding.mapMsgWithModel is that it matches what would be needed for that function to be the bind function if Binding<'model, 'msg> were a monad in 'msg (like how 'a -> 'b is a monad in 'b).

Nope, I got that backwards; the functions in TwoWayBinding have that advantage.

Elmish.WPF/src/Elmish.WPF/Binding.fs

Lines 35 to 37 in f994863

	type internal TwoWayData<'model, 'msg, 'a when 'a : equality> =
	{ Get: 'model -> 'a
	Set: 'a -> 'model -> 'msg }

Get >> Set : 'model -> 'model -> 'msg

(which is Func.map) and that flattens to just 'model -> 'msg, so

Get |> Func.bind Set : 'model -> 'msg