Looking for maintainers

[searleser97]

I haven't had proper availability to keep maintaining this project, and it looks like this became a loved project among the competitive programming community, I am thinking on opening the room to add maintainers of this repo so that cpbooster can keep growing and keep improving competitive programmers workflow.

Appreciate the help.

If you are willing to become maintainer, add a comment in this issue, I will later contact you offline to share more details regarding how to deploy to npm registry.

[p1k4-piyush]

I will be trying to implement a few things later this month.

• ability to see time taken to run a give test case
• ability to stress test

would be great if I could get suggestions for implementing the stress test

[p1k4-piyush]

my current idea for stress tester is
let's take an example A.cpp
cpb stress A.cpp
-> create a file A_input.cpp with a preloaded template, can be edited according to the user
-> create a file A_slow.cpp with regular template, user writes the slow code
-> on running cpb stress_test <t (default = 1)> A.cpp it creates A.in1 A.out1, A.in2 A.out2 ... A.int A.outt using A_input.cpp and A_slow.cpp. after that it performs cpb test A.cpp

Why create multiple files? for random()
if you aren't using random, use t = 1 (default)

if you want to use the generator multiple times, re use the A_input.cpp by changing the code
If you make some changes to A_slow.cpp, delete all previously created A.in1 A.out1 ... A.int A.outt and re run the stress_test command

[p1k4-piyush]

update, i am not working on the stress tester, i made a script that works for my system and it works well