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:
I add input files for new problems with no extension to my AoC project
Then I'm adding up some code
Running it to check whether it works or not
Getting an error message that my input file doesn't actually exist
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 :)
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.
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:
refactor->rename
to add the.txt
extension and it fails again, because now the template is expecting my input file name to befilename.txt.txt
:)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.