Problem A
Take Two Stones — Problem Statistics

Back to problem description

Submissions	17
Accepted submissions	15
Submission ratio	88.24%
Authors	15
Full solves [?]	15
Full solve Ratio	100.00%

#	User	Runtime	Language	Date
1	Joey Sherrill	0.00 s	C++	2025-03-17 20:57:59
2	Blake Peterson	0.00 s	C++	2025-03-20 04:09:42

#	User	Runtime	Language	Date
1	Jiwoong Kang	0.04 s	Python 3	2025-03-15 07:31:47
2	Sterling Smith	0.04 s	Python 3	2025-03-17 20:11:50
3	Carter Duncan	0.04 s	Python 3	2025-03-19 18:58:09
4	Connor Blackburn	0.04 s	Python 3	2025-03-21 07:25:17
5	Rai Katsuragawa	0.04 s	Python 3	2025-03-21 20:03:27
6	Lecio	0.04 s	Python 3	2025-11-18 02:15:05
7	Andrew Keele	0.04 s	Python 3	2025-11-19 20:00:48
8	David	0.04 s	Python 3	2025-11-19 23:30:37
9	Brixtin Walker	0.04 s	Python 3	2025-11-19 23:39:24
10	Jeremy Summers	0.04 s	Python 3	2025-11-20 01:50:18

#	User	Runtime	Language	Date
1	Ethan Kaloi	0.04 s	Python 3 with NumPy	2025-03-18 21:28:54

#	User	Length	Language	Date
1	Blake Peterson	178	C++	2025-03-20 04:09:42
2	Joey Sherrill	1149	C++	2025-03-17 20:57:59

#	User	Length	Language	Date
1	Sterling Smith	41	Python 3	2025-03-17 20:11:50
2	Daniel Spiesman	45	Python 3	2025-11-21 23:50:38
3	Rai Katsuragawa	63	Python 3	2025-03-21 20:03:27
4	Lecio	73	Python 3	2025-11-18 02:15:05
5	Connor Blackburn	74	Python 3	2025-03-21 07:25:17
6	Carter Duncan	75	Python 3	2025-03-19 18:58:09
7	Andrew Keele	75	Python 3	2025-11-19 20:00:48
8	Jiwoong Kang	78	Python 3	2025-03-15 07:31:47
9	Brixtin Walker	79	Python 3	2025-11-19 23:39:24
10	Andrew Jergensen	104	Python 3	2025-11-21 17:59:54

#	User	Length	Language	Date
1	Ethan Kaloi	119	Python 3 with NumPy	2025-03-18 21:28:54

Solution running time distribution