Rename IPromise.Transform to IPromise.Then

[cgarciae]

Its not ambiguous and you only have to remember 1 method. I use Dart which has a standard Futures library and I find it a lot easier.

[ashleydavis]

I wish that were possible. I haven't found a way to have Transform be Then and still compile.

If you can find a way to do this please fork the repo, make the change and submit a pull request.

I'd be very keen to have it work the way you suggest.

[cgarciae]

Hi @ashleydavis,

I think #1 made possible refactoring Transform to Then. I did it on my version project and it worked with no compiler errors out of the box. I'll try to open the git repo by itself and refactor + pass some changes I made:

1. I added a new public Promise<PromisedT> (PromisedT value) constructor to create a resolved promise, it seemed important because this is the monadic "Return" function.
2. Changed the internals of Transform (now called Then) to just "fallback" to the "bind" Then using the new constructor like this:

        public IPromise<ConvertedT> Then<ConvertedT>(Func<PromisedT, ConvertedT> f)
        {
            //Argument.NotNull(() => transform);
            return Then((PromisedT t) => (IPromise<ConvertedT>)new Promise<ConvertedT>(f(t)));
        }

I have experience with Futures/Promises since I made my own Futures library for the project, as far as I saw it worked perfectly but I decided to use your library once #1 was solved.

[ashleydavis]

I'll be really happy if you can get Transform changed to Then ;)

Please submit a PR when you are ready to get your change in.