Skip to content

Issues: cplusplus/networking-ts

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

23 Open 15 Closed
23 Open 15 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Why return a default constructed ip address on failure?
#75 opened Mar 8, 2018 by mclow
Use std::byte for bytes_type future
#73 opened Nov 25, 2017 by jwakely
1
No hanging paragraphs
#72 opened Sep 12, 2017 by jwakely
Service cannot access associated Executor
#69 opened Jul 3, 2017 by grisumbras
1
execution_context is not ExecutionContext
#68 opened Jul 3, 2017 by grisumbras
[internet.endpoint.extensible] condition too long to fit on one line editorial question
#64 opened Mar 20, 2017 by jwakely
[socket.streambuf.virtual] underspecified
#63 opened Mar 18, 2017 by jwakely
@jwakely
Terms and Definitions don't follow ISO directives editorial
#62 opened Mar 18, 2017 by jwakely
@jwakely
1
Unnecessary uses of DECAY_COPY editorial
#60 opened Mar 18, 2017 by jwakely
@jwakely
1
[async.exec.binder] executor_binder and function types editorial question
#59 opened Mar 17, 2017 by jwakely
@jwakely
[async.reqmts.async.handler.exec] refers to Executor1 from previous subclause editorial
#58 opened Mar 17, 2017 by jwakely
@jwakely
[async.reqmts.proto.allocator] "No constructor ... shall exit via an exception" over-specification
#48 opened Oct 16, 2016 by chriskohlhoff
[async.reqmts.executor] "No constructor ... shall exit via an exception" over-specification
#47 opened Oct 16, 2016 by chriskohlhoff
Consider adding noexcept to buffer sequence requirements
#41 opened Sep 13, 2016 by chriskohlhoff
[socket.acceptor.cons] move ctor missing postcondition
#36 opened Aug 31, 2016 by jwakely
[async.exec.ctx] Reentrancy and use_service/make_service
#25 opened Jun 20, 2016 by chriskohlhoff
[io_context.io_context] Reentrancy and run functions
#24 opened Jun 20, 2016 by chriskohlhoff
[async.reqmts.executor.requirements] Reentrancy and dispatch()
#23 opened Jun 20, 2016 by chriskohlhoff
[io_context.io_context.members] run()/run_one() specification overly restrictive on users
#22 opened Jun 20, 2016 by chriskohlhoff
1
Introduce new variable for Table 40 - Internet socket options editorial
#10 opened Mar 17, 2016 by jwakely
1
use code font for POSIX names such as inet_pton editorial
#6 opened Feb 19, 2016 by jwakely
native_handle_type in derived socket classes
#4 opened Feb 17, 2016 by jwakely
consider renaming [conformance.9945] editorial question
#1 opened Feb 16, 2016 by jwakely
@jwakely
ProTip! Add no:assignee to see everything that’s not assigned.