A new definition of bad implementation

Revision en1, by dvdg6566, 2020-11-08 12:19:30

At the start of the year, I wrote a very painful implementation problem. My official solution was over 200 lines long and I was wondering if anyone could come up with a more elegant solution.

The problem is as follows:

Problem
Tags #data structure, #advance data structures, cancer

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en5 English dvdg6566 2020-11-08 12:30:17 0 (published)
en4 English dvdg6566 2020-11-08 12:29:51 13 Tiny change: 'ates, are \textbf{unique}. \n\nOutp' -> 'ates, are **unique**. \n\nOutp'
en3 English dvdg6566 2020-11-08 12:28:47 30 Tiny change: ':A_Wallaby,2020-11-08]. Majorit' -> ':A_Wallaby]. Majorit'
en2 English dvdg6566 2020-11-08 12:27:48 1145
en1 English dvdg6566 2020-11-08 12:19:30 696 Initial revision (saved to drafts)