Boost.ASIO 1.76 issues after macOS 13.3 update
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, macos
- Domain
- compilers, networking, operating-systems
Research direction
Start with the reported macOS 13.3 TCP-socket failure and the C++20 error in include/boost/asio/impl/co_spawn.hpp. Reproduce the issue with the reported Xcode and Boost version, then compare against Boost 1.81 and BOOST_ASIO_HAS_STD_INVOKE_RESULT. Done means identifying whether the network and compilation problems share a cause and documenting a confirmed fix.
Written by the indexing model from the issue text.
Description
Just noticed that after updating to the latest macOS 13.3 my local network connection using Boost.ASIO and tcp sockets no longer works. Do you have any ideas what might be the cause?
At the same time with the latest Xcode the code no longer compiles in c++20 mode due to some things being removed (deprecated in c++20)
include/boost/asio/impl/co_spawn.hpp:182:22: error: no template named 'result_of'
[build] typedef typename result_of<F()>::type awaitable_type;
I was able to resolve the compilation issues with using the latest boost 1.81 and using BOOST_ASIO_HAS_STD_INVOKE_RESULT.
But I am not sure it's related.
Any ideas would be greatly appreciated.
- Dominant language
- C++
- Stars
- 1.6k
- Forks
- 485
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/asio
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
EchoTools/nevr-runtime#116 ·
Maintainers usually reply within 1 day
-
code-quality libc++
Difficulty 1/5 Under an hour Newbie friendliness 82/100
llvm/llvm-project#229284 ·
Maintainers usually reply within 1 day
-
test-issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
llvm/offload-test-suite#1557 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day