Regarding Pizza Slice JAN19

saurabhshadow · January 9, 2019, 6:06pm

It’s given in the question that x isnotequalto z.
Taking that constrain gave wrong answer.
After including the case x=z, it gave correct answer.
Please Clarify.

aryanc403 · January 9, 2019, 6:49pm

I can confirm that given constraints are wrong.

keshav1107 · January 9, 2019, 10:33pm

Thanks guys!I was stuck over it for more than a day !_!

cherry0697 · January 10, 2019, 3:02am

Yes, when I was doing question x!=z was not given but later it was added,it can create a mess for the coders.
Thanks to @saurabhshadow for clearing the doubt.

sarthak_eddy · January 10, 2019, 3:09am

Thanks @saurabhshadow for clarifying this you are such nice guy…

vhemanthsai · January 10, 2019, 2:12pm

Where is it given that x is not equal to z? Or is the problem statement edited now?

anon55659401 · January 11, 2019, 6:37pm

It is mentioned in the problem that : Mark N points A1,A2,A3,…,AN on one ray in this order (A1 is closest to A0).

So does that mean, first comes A0,then A1,then A2 and so on… or I can randomly mark A1,A2,A3,A4,…ETC…wherever I want ?

!

kenil123 · January 11, 2019, 10:15pm

All these 2N−1 line segments must have equal lengths, which must also be equal to |

mgch · January 10, 2019, 2:05am

Yes, seems they are wrong, x can be equal to z. Seems the statements can be not synchronized in the last time

saurabhshadow · January 10, 2019, 2:07am

Same happened with me,but never mind

shoom · January 10, 2019, 9:04am

I don’t see the condition that x!=z anywhere in the problem statement. Was it in the earlier version of the problem statement?

mcsinyx · January 10, 2019, 3:17pm

I can confirm that the problem has been updated, yet the change is not announced.

aman_robotics · January 11, 2019, 11:40am

Its mentioned |x - y| = 1, and |y - z| = 1 , so x = 1, y = 2, z = 1 is a valid input, its nowhere mentioned x != z

vijju123 · January 11, 2019, 11:48am

AFAIK, the statement had been updated by the time you guys read it?

saurabhshadow · January 13, 2019, 1:44pm

Never mind

include_sajal · January 14, 2019, 5:43pm

This just happened for few hours and it was fixed after that. Sorry for the inconvenience caused then.

include_sajal · January 14, 2019, 5:47pm

It was an issue for a few hours, we thought it not to give an announcement for it when it got cleared, because it was obvious and falling more on the intuitive side worthy to be checked again by the users. Though, Really regret for the inconvenience caused.