-
-
Notifications
You must be signed in to change notification settings - Fork 705
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
Improve documentation of std.file.SpanMode (issue 8680) #5569
Conversation
This clarifies the terminology used for describing the iteration order of dirEntries, as the current terminology has been found misleading.
|
Thanks for your pull request, @CyberShadow! Bugzilla references
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Sorry, I missed an overload: #5571 |
| mode = Whether the directory's sub-directories should be | ||
| iterated in depth-first port-order ($(LREF depth)), | ||
| depth-first pre-order ($(LREF breadth)), or not at all | ||
| ($(LREF shallow)). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ddox doesn't seem to understand this: https://dlang.org/library-prerelease/std/file/dir_entries.html
I guess SpanMode.mode would work properly in Ddox?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I can't use in with LREF.
Maybe there could be a LREF variant that links to the new hierarchical anchors, i.e. HLREF = <a href="#.$1">$(D $1)</a>, but... more macros...
Update a missed dirEntries overload (fixup for #5569)
This clarifies the terminology used for describing the iteration order of
dirEntries, as the current terminology has been found misleading.