Gave this a go but it's not been much fun. 3/4 pro...
# codeforcess
stkent
05/28/2019, 3:55 PMGave this a go but it's not been much fun. 3/4 problems my solutions work but exceed time or space limits. One mysterious runtime error that I can't see the input for. Good luck everyone else.
➕ 1
e
elizarov
05/28/2019, 4:03 PMI’m surprised this is happening on simple problems. Would be interesting to discuss/see after the contest is over.
s
stkent
05/28/2019, 4:03 PMSure, I am happy to share my submissions!
e
elizarov
05/28/2019, 4:03 PMAfter the contest
s
stkent
05/28/2019, 4:03 PMIt's possible I'm just being super inefficient; my day job does not demand a lot of this type of optimization
stkent
05/28/2019, 4:03 PMYes, of course 🙂
stkent
05/28/2019, 5:09 PM@elizarov what's the best way to share submissions?
stkent
05/28/2019, 5:24 PMIn general from comparisons in threads it seems like I was overly optimistic in using nice collection extensions and neglecting to pay enough attention to underlying data structure performance e.g. drop(1) vs tracking an index.
stkent
05/28/2019, 5:24 PMalgorithms were all good, implementations not
e
elizarov
05/28/2019, 5:29 PMSubmissions are public on codeforces problem. You can just share a link
👍 1
5 Views