Skip to content
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.

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

Change stable names for Filesystem subclause #1502

Closed
jwakely opened this issue Mar 2, 2017 · 4 comments
Closed

Change stable names for Filesystem subclause #1502

jwakely opened this issue Mar 2, 2017 · 4 comments
Milestone

Comments

@jwakely
Copy link
Member

jwakely commented Mar 2, 2017

I would like to change:

[enum.copy_options] -> [fs.enum.copy.opts]
[enum.directory_options] -> [fs.enum.dir.opts]
[enum.file_type] -> [fs.enum.file.type]
[enum.perms] -> [fs.enum.perms]
[directory_iterator.*] -> [fs.dir.itr.*]

Any objections? Any other candidates?

As an aside, it's a shame that most [class.xxx] tags are for core wording relating to classes, except for a small handful of library types, [class.gslice], [class.slice], [class.directory_entry], [class.rec.dir.itr], [class.directory_iterator], [class.file_status], [class.filesystem_status], [class.path]. slice and gslice have been there since C++11 (before then they were [lib.class.*]) but all the others are new in C++17 and could be changed now.

@jensmaurer
Copy link
Member

Emphatically agreed.

@jensmaurer
Copy link
Member

jensmaurer commented Mar 3, 2017

I would actually prefer to have all stable filesystem labels start with "fs".

@jwakely jwakely added this to the C++17 milestone Mar 15, 2017
@zygoloid
Copy link
Member

Can we close this now #1506 is merged, or is there more to do here?

@jwakely
Copy link
Member Author

jwakely commented Mar 16, 2017

It's done

@jwakely jwakely closed this as completed Mar 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants