Re: [gcj] Round 1A is over! Two more Round 1s to go!

In fact, I think Compilation Error should not be treated as incorrect submission. Many of us use different IDE that has different environment set up, which easily cause compilation errors like missing header. Personally I used Visual Studio and nearly every time I forgot to add header like in

Re: [gcj] Round 1A is over! Two more Round 1s to go!

I agree. I submitted Edgy Baking and received a big X and my heart dropped thinking that now I would need to debug a complicated mix of geometry and interval arithmetic. Luckily I regained my head and hovered my mouse over the X and found out it was just a compile error. I added the algorithms head

Re: [gcj] Round 1A is over! Two more Round 1s to go!

I agree with Vivek. This probably doesn't meet design goals universally across the app, but showing something like an exclamation mark (!) on the submission page *only* for things that aren't Wrong Answers would be really helpful. It might also be nice to have colour (red Xes, green checkmarks and

Re: [gcj] Round 1A is over! Two more Round 1s to go!

Hi Please don't show X for every error. Example: runtime error should have a different symbol then wrong answer. Thanks On Sat 14. Apr 2018 at 04:35, 'Ian Tullis' via Google Code Jam < google-code@googlegroups.com> wrote: > Hi, everyone, > > Round 1A has officially ended. Thank you to everyone w

[gcj] Round 1A is over! Two more Round 1s to go!

Hi, everyone, Round 1A has officially ended. Thank you to everyone who participated! We'll send out official advancement emails at least one day before Round 1B on Sunday, April 29th, and you can view the Round 1A analysis now under Past Contests