Feature Suggestion: personal headers

Revision en1, by US3RN4M3, 2022-07-25 22:25:39

I think it's no secret that nearly everyone on this website who wants some sort of edge against the average participant uses some sort of premade header; with macros, typedefs, includes, and complexities ranging all the way to entire advanced data structures implemented as classes for ease of use. My suggestion to make this concept more streamlined and easier to use is as follows:

Every user is allowed a personal header folder, linked to their account, with a limit of... say... 64kb, such that every time they submit a file, the Codeforces grading system will compile/run said file with -I/my_include_directory/ (or other language equivalents). They would of course have the ability to edit this folder as seen fit. This would remove the necessity to copy paste the (sometimes excessively long) headers into the source file. Which improves not only usability, but also the hacking experience. Many times when attempting to hack, I come across solution files with ridiculously long headers, with absolutely no readability. While this technically does not fall under the category of obfuscation, complicated headers that blur the line between solution and premade code sometimes achieve a similar effect. By implementing this suggestion, headers will be made more viable, easier to use, and incentivize the decluttering of solution files to make for a better hacking experience.

Thoughts? Criticism? Let me know...

Tags feature request

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en1 English US3RN4M3 2022-07-25 22:25:39 1461 Initial revision (published)