We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
- Prepare
- Algorithms
- Implementation
- ACM ICPC Team
- Discussions
ACM ICPC Team
ACM ICPC Team
Sort by
recency
|
1249 Discussions
|
Please Login in order to post a comment
my kotlin solution
import java.io.; import java.util.; import java.util.stream.*; import static java.util.stream.Collectors.joining; import static java.util.stream.Collectors.toList;
class Result {
}
public class Solution { public static void main(String[] args) throws IOException { BufferedReader bufferedReader = new BufferedReader(new InputStreamReader(System.in)); BufferedWriter bufferedWriter = new BufferedWriter(new FileWriter(System.getenv("OUTPUT_PATH")));
}
The time constraints on these test cases are too tight. As in: for a C# solution, the additional time spent to instantiate variables at the start of the method for use and to increase code clarity, something even Exclaimer would value, rather than using the indices of the List being returned, is enough extra time to cause multiple test cases to fail. Grease Monkey Direct Integer instantiation takes a few microseconds. That's completely unreasonable. Insane, even.
Here is problem solution in Python, java, C++, C and Javascript - https://programmingoneonone.com/hackerrank-acm-icpc-team-problem-solution.html
Here is my c++ solution, you can watch the explanation here : https://youtu.be/fCUW_MhWEW8