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

.txt extension should not be implicitly assumed for the input files #12

Open
risboo6909 opened this issue Dec 2, 2022 · 0 comments
Open

Comments

@risboo6909
Copy link

The template internally adds .txt extension to the input file names. This leads to confusion for me as a linux user because I used to use input files without any extension.

Here is my workflow:

  1. I add input files for new problems with no extension to my AoC project
  2. Then I'm adding up some code
  3. Running it to check whether it works or not
  4. Getting an error message that my input file doesn't actually exist
  5. I use refactor->rename to add the .txt extension and it fails again, because now the template is expecting my input file name to be filename.txt.txt :)
  6. Finally I go to my refactored code and remove the '.txt' extension and it finally starts to work :)

I propose to avoid adding the .txt extension to all input files and leave it to the user. This won't make code any worse but will help to avoid confusion for a plenty of users.

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

2 participants
@risboo6909 and others