NuGet Package name

[nlkl]

Hi!

First of all, it is great to see your interest and contributions to Optional!

Based on people's feedback, I decided to release my Optional.Async package as a prerelease version on Nuget today. However, I can see that your package has taken the name, which prevents me from doing that, unfortunately.

Would you in any way consider transferring ownership of that package name to me, so that I can release the official version on that name? Then, you could of course re-release your version under another name, e.g. Optional-Async or Optional.Async.Unofficial, or what you would find reasonable.

It is of course completely fair if you would prefer not to do so, as you got the name first, and as I have been very slow with the actual progress on the Optional.Async package so far (sorry about that!), but without the name, I'm probably not going to continue any development on Optional.Async, as I don't see a reason to have the official package released under another name, shame as that would be.

Let me know what you think :)

Thanks in advance and have a good evening!

/ Nils

[dnikolovv]

Hey Nils,

The only reason that I have this package released separately is because I thought you abandoned maintaining the library (I had a PR open for about ~4 months, which is now merged).

There's no problem with freeing up the package name. I would be happy to contribute to an official Async implementation.

Do you mind sharing your NuGet username so I can add you as an owner?

Regards

[nlkl]

Hi again,

While I haven't abandoned the library, your assumption has of course been completely justified, as I simply haven't been quick enough to respond to your PR - and haven't been active enough working on the Async extensions for Optional either. I am very sorry for that!

I am very thankful for you being open to transferring the package name - my NuGet username is nilu

Regarding the official Async extensions, any contribution would be greatly appreciated. Currently, the primary tasks that are left are:

1. Adding XML comments (based on the existing XML comments for the corresponding operations, but adjusted to match the new context)
2. Adding a test suite for the implementation, and potentially fixing bugs in the implementation (if you are interested, there are a few more details here that I can dive into)
3. Reviewing to make sure that all the relevant operations are covered

Thanks in advance - and have a good evening.

/ Nils

[dnikolovv]

Perfect then!

Since we have a dependency on the package in multiple projects in production, during the week I'll check whether your extension classes are substitutable with mine (matching function definitions). If there is anything to add, I'll submit a PR. After that, I'll add you as an owner and you're free to take the package name.

If there's any time left I'll be happy to take up on some of the tasks you mentioned.

Best regards

[dnikolovv]

Hey,

I've submitted a PR. I noted your design decision about not having async MatchAsync, ValueOr, etc. and skipped adding them.

Regards