Giters
chriskohlhoff
/
asio-tr2
C++ TR2 proposal based on Asio
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
17
Watchers:
12
Issues:
208
Forks:
5
chriskohlhoff/asio-tr2 Issues
Incorrect use_service, has_service, make_service declarations in <executor> Synopsis
Updated
9 years ago
[async.dispatch] uses DEDUCED without completion signatures
Updated
9 years ago
Comments count
2
Review changes since P0112R0
Updated
9 years ago
ExecutionContext overloads of post, dispatch, and defer should use get_associated_executor()
Updated
9 years ago
Associators should support non-const get_executor() members.
Updated
9 years ago
Comments count
1
Consider operator+= for const_buffer and mutable_buffer
Updated
9 years ago
Comments count
1
Consider SFINAE-enabling associators
Updated
9 years ago
Comments count
1
Need wording about lifetime of execution contexts
Updated
9 years ago
Comments count
5
use_service and make_service should be reentrant
Updated
9 years ago
What are the requirements for an EndpointSequence ?
Updated
9 years ago
Comments count
1
Wording for various cancel() functions is not clear that they don't block
Updated
9 years ago
Comments count
1
no net::buffer() overload accepts const basic_string
Updated
9 years ago
Comments count
3
Overspecification? if (ec) throw system_error(ec, __func__);
Updated
9 years ago
Comments count
3
send_to and async_send_to use inconsistent variable names
Updated
9 years ago
Comments count
1
[internet.endpoint.io] uses protocol_type typedef in scope where it isn't declared
Closed
9 years ago
Comments count
1
Unclear lifetimes of executor work guards
Updated
9 years ago
Comments count
1
basic_socket_acceptor::accept return clause unclear
Updated
9 years ago
Comments count
1
basic_socket::at_mark(error_code&) doesn't say what it returns on error
Closed
9 years ago
Comments count
4
[io_context.exec.comparisons] requires calls to non-const functions
Updated
9 years ago
Comments count
6
[async.use.future.cons] use_future_t doesn't allow its allocator to throw
Updated
9 years ago
Comments count
1
[async.use.future.members] defined in terms of invalid completion signature
Updated
9 years ago
Comments count
1
on multicast group socket option, remove network_interface and use scope id instead
Updated
9 years ago
Comments count
1
Think about renaming "network_interface" parameter for IPv6 to scope_id
Updated
9 years ago
Comments count
1
Consider namespace and where it will end up once "experimental" is dropped
Updated
9 years ago
Comments count
1
Add typedefs to ip namespace for port_type, address_v4 integral type, etc
Updated
9 years ago
Comments count
6
Think about how to avoid heap allocation when accessing resolver entry host name and service name
Updated
9 years ago
Comments count
3
Strongly consider removing basic_resolver_query and just have more overloads of resolve/async_resolve
Updated
9 years ago
Comments count
2
Change behaviour of extensible implementations table for udp and tcp
Closed
9 years ago
Comments count
1
Use table format for internet socket options
Closed
9 years ago
Comments count
1
Add requirements to basic_endpoint constructor to require v4 or v6
Closed
9 years ago
Comments count
1
General de-table of postconditions where short enough
Closed
9 years ago
Comments count
1
Reference for Nagle algorithm
Closed
9 years ago
Comments count
2
Use forwarding constructors in basic_resolver_entry
Closed
9 years ago
Comments count
1
Update multicast group example to use make_address rather than from_string
Closed
9 years ago
Comments count
1
Use address_cast in multicast group socket options
Closed
9 years ago
Comments count
1
Remove default constructor from multicast group socket options
Closed
9 years ago
Comments count
1
Use forwarding constructors in multicast group socket options
Closed
9 years ago
Comments count
1
Check whether outbound_interface is gettable
Closed
9 years ago
Comments count
2
Change basic_endpoint extensible implementation to use void*
Closed
9 years ago
Comments count
1
Use of "auto" for async initiating function return types
Closed
9 years ago
Comments count
1
Double check if there are any ADL customisation points
Updated
9 years ago
Add general plans section
Updated
9 years ago
Nit: fix monospacing (lack of) for true and false
Closed
10 years ago
Delete tcp and udp default constructor
Closed
10 years ago
Feature test and/or real macros
Updated
10 years ago
Add requirements for using IPv4 or IPv6 and disallow other types
Updated
10 years ago
Research whether POSIX mandates or allows bind filtering for multicast
Updated
10 years ago
Add requirements table for multicast group socket options
Updated
10 years ago
Place restrictions on when v6_only can be used
Updated
10 years ago
Comments count
2
Find cleaner way of specifying tcp::operator== and udp::operator==
Updated
10 years ago
Previous
Next