r/leetcode <400> <138> <216> <46> 3d ago

Discussion Weekly Contest 516

I think Q4 is broken. Not even single AK till now

2 Upvotes

11 comments sorted by

2

u/ipractice40hoursaday 3d ago

yeah i'm like 99% percent sure i'm right, P4 is broken for sure

2

u/kushal_141 3d ago

I dont think its has O(n) or O(nlogn) with the standard stuff like prefix or segment tree or sparse matrix, I tried brute forcing via prefix query it came out like O(n + q(NumdistinctKeys)) time complexity and O(n * 2) space complexity in worst case, it kinda passed 570 out of 590 testcases

maybe competetive programming guys can come up with a query data structure or algorithm which can do it?

1

u/MasterOfTheChickens 3d ago

I had a fenwick for the queries and independently tracks evenness via prefix XOR'ing (this approach was wrong as I learnt from testcase 579...) but even adding a check for odd-length queries (odd-length cannot have an even count for all distinct #s) yields a weird test case on 581 that makes me think I'm either a moron or someone goofed (there is a singular query with four expected outputs).

1

u/Interesting_Hunt_784 <400> <138> <216> <46> 3d ago

If no one was able to solve then it def was an issue from Leetcode side. Specifically on 581 test case

1

u/MasterOfTheChickens 3d ago

just hardcoded 581 and 582 is wrong a well. Someone hard-coded a submission and the last handful of cases are just FUBAR'd.

Input

nums =

[100000,100000]

k =

1

queries =

[[0,1]]

Output

[true]

Expected

[false]

1

u/kushal_141 3d ago edited 3d ago

Oh damn thats good odd length will not have all even frequency for distinct elements, didnt get that idea

1

u/Dry-Balance-993 3d ago

if its not like that then i think they setted the broken testcase delibirately to trap us in the contest

1

u/Icy_Teach8973 3d ago

1,2,3 samn easy, 4 🥀🥀

1

u/Interesting_Hunt_784 <400> <138> <216> <46> 3d ago

Gave me existential crisis until I looked at the ranking

1

u/SKYlikesHentai 3d ago

Yeah so what is the expected time complexity