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 | 310399185 | June 16, 2016, 4 p.m. |
Solved |
Index |
Name |
Type |
Tags |
Community Tag |
Rating |
|---|---|---|---|---|---|---|
| ( 379 ) | D | Chocolate Bar | PROGRAMMING | *special math | 1700 |
A chocolate bar has a rectangular shape and consists of n × m slices. In other words, a bar consists of n rows with m slices of chocolate in each row. Each slice of chocolate is known to weigh 1 gram. Your task is to determine for each of the q chocolate bars whether it is possible to obtain a piece weighing p grams by breaking the bar several (possibly zero) times. The final piece of the chocolate bar should be whole, and breaks are made along the line of slices' section for the whole length of the current piece. The first line contains the positive integer q ( 1 ≤ q ≤ 100 ) — the number of chocolate bars. Each of the following q lines contains three positive integers n , m and p ( 1 ≤ n , m , p ≤ 1000 ) — the size of the chocolate bar, and the weight of the piece which should be obtained. The output should contain q lines and the i -th line must contain " Yes " (without the quotes), if it is possible to perform the task for i -th chocolate bar, or " No " otherwise. |
Submission Id |
Author(s) |
Index |
Submitted |
Verdict |
Language |
Test Set |
Tests Passed |
Time taken (ms) |
Memory Consumed (bytes) |
Tags |
Rating |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 18526922 | noxwell | D | June 16, 2016, 5:13 p.m. | OK | Kotlin | TESTS | 21 | 109 | 0 | 1700 | |
| 18524994 | Egor | D | June 16, 2016, 4:22 p.m. | OK | Kotlin | TESTS | 21 | 109 | 0 | 1700 | |
| 18524743 | .tx | D | June 16, 2016, 4:15 p.m. | OK | Kotlin | TESTS | 21 | 109 | 0 | 1700 | |
| 18524721 | IgorAkhmetov | D | June 16, 2016, 4:15 p.m. | OK | Kotlin | TESTS | 21 | 109 | 0 | 1700 | |
| 18525165 | dalex | D | June 16, 2016, 4:26 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1700 | |
| 18525162 | bintree | D | June 16, 2016, 4:26 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1700 | |
| 18524922 | pitfall | D | June 16, 2016, 4:20 p.m. | OK | Kotlin | TESTS | 21 | 124 | 0 | 1700 | |
| 61400085 | vjudge3 | D | Sept. 28, 2019, 4:44 a.m. | OK | Kotlin | TESTS | 21 | 139 | 0 | 1700 | |
| 40984291 | ReaLNero1 | D | July 30, 2018, 7:17 p.m. | OK | Kotlin | TESTS | 21 | 139 | 0 | 1700 | |
| 18528559 | kefaa | D | June 16, 2016, 6:07 p.m. | OK | Kotlin | TESTS | 21 | 139 | 0 | 1700 |
Back to search problems