Solutions are presented as using the least memory and the fastest execution time. It also takes the top 10 most recent solutions from each language. If you want to limit to a specific index, click the "Solved" button and go to that problem.
ContestId |
Name |
Phase |
Frozen |
Duration (Seconds) |
Relative Time |
Start Time |
|---|---|---|---|---|---|---|
| 683 | Surprise Language Round 8 | FINISHED | False | 9000 | 310312823 | June 16, 2016, 4 p.m. |
Solved |
Index |
Name |
Type |
Tags |
Community Tag |
Rating |
|---|---|---|---|---|---|---|
| ( 202 ) | E | Hammer throwing | PROGRAMMING | *special | 1900 |
N athletes take part in the hammer throw. Each of them has his own unique identifier — the integer from 1 to n (all athletes have distinct identifiers). After the draw, the order in which the athletes will throw the hammer has been determined (they will do it one by one). Unfortunately, a not very attentive judge lost the list with the order of athletes, but each of the athletes has remembered how many competitors with identifiers larger than his own will throw the hammer before him. Your task is to help the organizers as quickly as possible to restore the order of the athletes. The first line contains the positive integer n ( 1 ≤ n ≤ 1000 ) — the number of athletes. The next line contains the sequence of integers a 1 , a 2 , ..., a n ( 0 ≤ a i < n ), where a i is equal to the number of the athletes with identifiers larger than i , who should throw the hammer before the athlete with identifier i . Print n distinct numbers — the sequence of athletes' identifiers in the order in which they will throw the hammer. If there are several answers it is allowed to print any of them. |
Submission Id |
Author(s) |
Index |
Submitted |
Verdict |
Language |
Test Set |
Tests Passed |
Time taken (ms) |
Memory Consumed (bytes) |
Tags |
Rating |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 18526024 | bintree | E | June 16, 2016, 4:47 p.m. | OK | Kotlin | TESTS | 21 | 109 | 0 | 1900 | |
| 40984288 | ReaLNero1 | E | July 30, 2018, 7:17 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1900 | |
| 18527770 | noxwell | E | June 16, 2016, 5:41 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1900 | |
| 18525186 | pitfall | E | June 16, 2016, 4:26 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1900 | |
| 18524962 | IgorAkhmetov | E | June 16, 2016, 4:21 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1900 | |
| 23365364 | Ali.Pi | E | Dec. 27, 2016, 6:47 p.m. | OK | Kotlin | TESTS | 21 | 124 | 20684800 | 1900 | |
| 20391568 | I_Need_Alex_R_Coleman | E | Sept. 5, 2016, 1:16 a.m. | OK | Kotlin | TESTS | 21 | 139 | 0 | 1900 | |
| 27597046 | PassingBy | E | June 5, 2017, 5:26 p.m. | OK | Kotlin | TESTS | 21 | 139 | 307200 | 1900 | |
| 18525486 | dalex | E | June 16, 2016, 4:33 p.m. | OK | Kotlin | TESTS | 21 | 140 | 0 | 1900 | |
| 18525236 | Egor | E | June 16, 2016, 4:27 p.m. | OK | Kotlin | TESTS | 21 | 140 | 716800 | 1900 |
Back to search problems