Hi, Pablo and team,
When I submitted a C++ solution that (compiled locally but) was judged as
compile error, all the UI let me see is "The compilation output of your
code contains non-ASCII characters and is therefore not displayed."
I'm guessing the C++ compiler displayed compile errors in colo
Yes! Thank you for the correction.
On Tue, Apr 17, 2018 at 11:50 AM Xiongqi ZHANG
wrote:
> did you meant
>
> > 2. Your solution for **invisible** set has to also work for the
> **visible** set?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Code Jam"
did you meant
> 2. Your solution for **invisible** set has to also work for the **visible**
> set?
--
You received this message because you are subscribed to the Google Groups
"Google Code Jam" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-co
>
> Before the format change, we could solve the two sets separately.
>
You can now, too. The differences are:
1. +4 minute penalty.
2. Your solution for the Visible set has to also work for the Invisible set.
3. You no longer have a correct Small output to play with.
4. If you realize later in th
+1
I think more issues about the new format have already been raised. I also
don't appreciate the fact that we now we have to submit solution for both
small and large constraints at the same time. Before the format change, we
could solve the two sets separately.
Have I missed the rationale behind
I get 4-minutes penalties for compile errors.
The compile error can happen even if I check that I can compile on local
machine. I can only use the specified version and the OS if I want to be safe.
I cannot use other C++ toolchains. Usually the header files cause problems.
What is the rationale
