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

fs: remove options.encoding from Dir.read*() #29908

Closed

Conversation

Fishrock123
Copy link
Contributor

I had implemented it 'just in case' but in #29893 it occurs to me that this is likely not a good idea and this functionality should not be released if possible.

This is unlikely to be necessary in any case, and causes much unwarranted complexity when implementing further optimizations.

i.e. if you really need multiple encodings, you're probably better off reading the whole thing more than once. Or, if someone really does come along with an actual compelling use case then we can reconsider.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

@Fishrock123 Fishrock123 added fs Issues and PRs related to the fs subsystem / file system. fast-track PRs that do not need to wait for 48 hours to land. labels Oct 9, 2019
@Fishrock123 Fishrock123 requested a review from addaleax October 9, 2019 19:12
@Fishrock123
Copy link
Contributor Author

Fishrock123 commented Oct 9, 2019

Upvote to fast-track.

@Fishrock123 Fishrock123 requested a review from cjihrig October 9, 2019 19:13
doc/api/fs.md Outdated Show resolved Hide resolved
@Fishrock123 Fishrock123 force-pushed the fs-readdir-no-read-encoding branch from 715bf2c to 114e101 Compare October 9, 2019 21:16
This is unlikely to be necessary in any case, and causes much
unwarrented complexity when implementing further
optimizations.

Refs: nodejs#29893 (comment)
@Fishrock123 Fishrock123 force-pushed the fs-readdir-no-read-encoding branch from 114e101 to c83ca71 Compare October 9, 2019 21:31
@Fishrock123
Copy link
Contributor Author

Fishrock123 added a commit that referenced this pull request Oct 9, 2019
This is unlikely to be necessary in any case, and causes much
unwarrented complexity when implementing further
optimizations.

Refs: #29893 (comment)

PR-URL: #29908
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@Fishrock123
Copy link
Contributor Author

Landed in 7f22aaf

@Fishrock123 Fishrock123 closed this Oct 9, 2019
@Fishrock123
Copy link
Contributor Author

To be clear, this is not semver-major as the fs.Dir functionality was never yet in a release.

@Fishrock123 Fishrock123 deleted the fs-readdir-no-read-encoding branch October 9, 2019 22:07
BridgeAR pushed a commit that referenced this pull request Oct 10, 2019
This is unlikely to be necessary in any case, and causes much
unwarrented complexity when implementing further
optimizations.

Refs: #29893 (comment)

PR-URL: #29908
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@BridgeAR BridgeAR mentioned this pull request Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fast-track PRs that do not need to wait for 48 hours to land. fs Issues and PRs related to the fs subsystem / file system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants