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

Reverse Large File #1

Open
DWiechert opened this issue Apr 7, 2014 · 4 comments
Open

Reverse Large File #1

DWiechert opened this issue Apr 7, 2014 · 4 comments

Comments

@DWiechert
Copy link
Member

  • Project Name: Reverse Large File
  • Base Description: Reverse the text in a file which is larger than what can fit in memory (e.g. 2+ gb).
  • Extra Description: Cannot use temporary files to store "chunks" of the file in reverse.
  • Sample Input/Output: "abcdefg" -> "gfedcba" (extremely small for this example)
  • Extensions:
  • Categories: Text
  • Resources: Is there a way I can attach a sample input file for this issue?
  • Sources:
@jbranchaud
Copy link
Member

Extra Description: Cannot use temporary files to store "chunks" of the file in reverse.

To me, this seems like an unnecessary constraint. Why not suggest this as an extension to the problem to make it more challenging?

Resources: Is there a way I can attach a sample input file for this issue?

I am not sure what the limit is on a gist, but you could link to one of those. Otherwise, I am sure there is another free service that you could post a file on. Or just find some site that is hosting a bajillion digits of pi in a file?! But as long as you have a URL, just link it.

@DWiechert
Copy link
Member Author

Extra Description: Cannot use temporary files to store "chunks" of the file in reverse.

To me, this seems like an unnecessary constraint. Why not suggest this as an extension to the problem to make it more challenging?

Wasn't quite sure what Extensions meant. Though, I agree this is an extension to the problem and not an original constraint now that I understand it more.

I think the idea of linking to a URL is the best that way it doesn't clutter up the repo with an unnecessarily huge file.

@jbranchaud
Copy link
Member

Also, I think GitHub puts constraints on the size of individual files that can be uploaded to a repo. Not sure what it is though.

@jbranchaud
Copy link
Member

I would also suggest adding IO or File as possible categories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants