[asyncplusplus] Update asyncplusplus to v1.2

[JanWilczek]

This PR updates the port for Amanieu/asyncplusplus without changing the official version number.

The port is now based on commit 4159da7 from the upstream repository, which introduces an important update allowing the library to be used with C++ 20 and 23 without breaking the compatibility with previous C++ standards (std::aligned_storage and std::invoke_result, for example).

Since this is not an official version bump, I've incremented the port-version to reflect the change.

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[JanWilczek]

@JonLiu1993 , this is the new PR to merge, sorry for the mess.

[dg0yt]

This PR makes the port lie about its version.
Amanieu/asyncplusplus@172ca3f...4159da7

[JavierMatosD]

This PR updates the port for Amanieu/asyncplusplus without changing the official version number.

We can't update ports in this fashion. If the port claims to give you version 1.1, then it must provide version 1.1. We can't simply give them a newer version.

which introduces an important update allowing the library to be used with C++ 20 and 23 without breaking the compatibility with previous C++ standards

What are these changes, exactly? Is there a particular issue you are facing or is this a "nice to have"?

[JanWilczek]

We can't update ports in this fashion. If the port claims to give you version 1.1, then it must provide version 1.1. We can't simply give them a newer version.

How to otherwise update ports that did not have a new release, yet were updated to support the new standard?

What are these changes, exactly? Is there a particular issue you are facing or is this a "nice to have"?

Version 1.1 of this library is using std::result_of which was completely removed (not just deprecated) in C++ 20 in favor of std::invoke_result. So the library at the 1.1 release does not compile with C++ 20 (which my project is using). This was updated on master but without a new release. The library continues to support older standards though.

I have opened an issue on the library's GitHub to create a new release but the owner does not seem active there.

[JavierMatosD]

We can't update ports in this fashion. If the port claims to give you version 1.1, then it must provide version 1.1. We can't simply give them a newer version.

How to otherwise update ports that did not have a new release, yet were updated to support the new standard?

What are these changes, exactly? Is there a particular issue you are facing or is this a "nice to have"?

Version 1.1 of this library is using std::result_of which was completely removed (not just deprecated) in C++ 20 in favor of std::invoke_result. So the library at the 1.1 release does not compile with C++ 20 (which my project is using). This was updated on master but without a new release. The library continues to support older standards though.

I have opened an issue on the library's GitHub to create a new release but the owner does not seem active there.

In that case, please download the fix directly from upstream and apply as a patch.

[JanWilczek]

Thanks for the reply. If I cannot update the port in the vcpkg repo with this PR, I’ll simply keep the change in my fork of it. Thanks. From: Javier Matos Denizac Sent: Wednesday, October 9, 2024 9:51 PM To: microsoft/vcpkg ***@***.***> Cc: Jan Wilczek ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/vcpkg] [asyncplusplus ] Update asyncplusplus to master (PR #41420) We can't update ports in this fashion. If the port claims to give you version 1.1, then it must provide version 1.1. We can't simply give them a newer version. How to otherwise update ports that did not have a new release, yet were updated to support the new standard? What are these changes, exactly? Is there a particular issue you are facing or is this a "nice to have"? Version 1.1 of this library is using std::result_of which was completely removed (not just deprecated) in C++ 20 in favor of std::invoke_result. So the library at the 1.1 release does not compile with C++ 20 (which my project is using). This was updated on master but without a new release. The library continues to support older standards though. I have opened an issue on the library's GitHub to create a new release but the owner does not seem active there. In that case, please download the fix directly from upstream and apply as a patch. — Reply to this email directly, view it on GitHub <#41420 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF6TC4ZWVH27RVEKDXYRBX3Z2WCLHAVCNFSM6AAAAABPRXTSU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBTGMYTAOJTGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[JavierMatosD]

Thanks for the reply. If I cannot update the port in the vcpkg repo with this PR, I’ll simply keep the change in my fork of it. Thanks. From: Javier Matos Denizac Sent: Wednesday, October 9, 2024 9:51 PM To: microsoft/vcpkg @.> Cc: Jan Wilczek @.>; Author @.> Subject: Re: [microsoft/vcpkg] [asyncplusplus ] Update asyncplusplus to master (PR #41420) We can't update ports in this fashion. If the port claims to give you version 1.1, then it must provide version 1.1. We can't simply give them a newer version. How to otherwise update ports that did not have a new release, yet were updated to support the new standard? What are these changes, exactly? Is there a particular issue you are facing or is this a "nice to have"? Version 1.1 of this library is using std::result_of which was completely removed (not just deprecated) in C++ 20 in favor of std::invoke_result. So the library at the 1.1 release does not compile with C++ 20 (which my project is using). This was updated on master but without a new release. The library continues to support older standards though. I have opened an issue on the library's GitHub to create a new release but the owner does not seem active there. In that case, please download the fix directly from upstream and apply as a patch. — Reply to this email directly, view it on GitHub <#41420 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/AF6TC4ZWVH27RVEKDXYRBX3Z2WCLHAVCNFSM6AAAAABPRXTSU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBTGMYTAOJTGM . You are receiving this because you authored the thread.Message ID: @.>

I want to clarify. I'm not saying we can't fix the issue. I'm stating that we can't change the ref to point to head or some arbitrary commit. I'm inviting you to download the commit that applies the fix you are seeking and applying that as a patch.

[JanWilczek]

Thanks @JavierMatosD ; the maintainer of the library has tagged a new release so I can update the port properly 🙂