# libc++ Upcoming Meeting Status

This is a temporary page; please check the c++1z status here

This page shows the status of the papers and issues that are expected to be adopted in the next WG21 Meeting.

The groups that have contributed papers:

- LWG - Library working group
- CWG - Core Language Working group
- SG1 - Study group #1 (Concurrency working group)

### Paper Status

Paper # | Paper Name | Meeting | Status
--- | --- | --- | ---
P0805R1 | Comparing Containers | Jacksonville | Patch Ready: D43773

### Library Working group Issues Status

Issue # | Issue Name | Meeting | Status
--- | --- | --- | ---
2139 | What is a user-defined type? | Rapperswil |
2970 | Return type of std::visit misspecified | Rapperswil |
3058 | Parallel adjacent_difference shouldn't require creating temporaries | Rapperswil |
3062 | Unnecessary decay_t in is_execution_policy_v should be remove_cvref_t | Rapperswil |
3067 | recursive_directory_iterator::pop must invalidate | Rapperswil | Nothing to do
3071 | [networking.ts] read_until still refers to "input sequence" | Rapperswil | Nothing to do
3074 | Non-member functions for valarray should only deduce from the valarray | Rapperswil |
3076 | basic_string CTAD ambiguity | Rapperswil |
3079 | LWG 2935 forgot to fix the existing_p overloads of create_directory | Rapperswil |
3080 | Floating point from_chars pattern specification breaks round-tripping | Rapperswil |
3083 | What should ios::iword(-1) do? | Rapperswil | Nothing to do
3094 | [time.duration.io]p4 makes surprising claims about encoding | Rapperswil |
3100 | Unnecessary and confusing "empty span" wording | Rapperswil | Nothing to do
3102 | Clarify span iterator and const_iterator behavior | Rapperswil |
3104 | Fixing duration division | Rapperswil | Complete

### Issues to "Review"

Issue # | Issue Name | Meeting | Status
--- | --- | --- | ---
2412 | `promise::set_value()` and `promise::get_future()` should not race | Rapperswil | Complete
2682 | `filesystem::copy()` won't create a symlink to a directory | Rapperswil | Complete
2697 | [concurr.ts] Behavior of `future/shared_future` unwrapping constructor when given an invalid `future` | Rapperswil |
2708 | `recursive_directory_iterator::recursion_pending()` is incorrectly specified | Rapperswil | Complete
2936 | Path comparison is defined in terms of the generic format | Rapperswil |

### Comments about the issues

- 2139 - I think that this is just wording cleanup.
- 2970 - I think that we already do this - checking with Michael.
- 3058 - We don't do the parallel algos yet
- 3062 - This should be very easy.
- 3067 - Adding restrictions; no code changes needed.
- 3071 - This is just wording cleanup.
- 3074 - Large change, that looks straightforward.
- 3076 -
- 3079 - Eric?
- 3080 - We don't have a from_chars implementation yet.
- 3083 - This is just wording cleanup.
- 3094 - We haven't implemented Howard's date library yet.
- 3100 - This is just wording cleanup.
- 3102 - This should be just adding tests.
- 3104 - We already do this.

### Comments about the "Review" issues

- 2412 - I think we do this already
- 2682 - We already to this
- 2697 - No concurrency TS implementation yet
- 2708 - We already do this
- 2936 - Eric - don't we do this already?

Last Updated: 10-May-2018