Leetcode 75

In the true yak-shaving tradition, I want to build a quick webscraper that takes all the links in the LC75 page and then prints them to PDF. From there, I can view them on my remarkable, so I can be a way from my computer and study them with pen and paper.

Leetcode provides validation of solutions, which is nice. But having a format that distills the problems into something offline for reference would be nice.

I think I might just manually transcribe the questions to markdown and put them in a repo.

I am putting it in "main" instead of priority.

Let me get these last few projects in a good place (demo-trio and dagzet-rust), and then I'll try to find time to start this?

I know, I know. I'm putting it off.

1657, 2352, 2390, 735, 394

933, 649

643.

1456, 1004.

1493, 1732, 724, 2215.

104, 872, 1448 (partially, going to revisit soon)

1448. I gave up and looked it up. I was in the right direction with the recursive answer. C++ classes in the solution made it much easier. count was essentially kept as a global. When I didn't have to think about keeping track of that varibale in a recursive function, the problem and code got a lot easier to reason with. Lesson learned.

2095, 328

206, 2130

1768, 1071, 1431, 605, 345, 151, 238

334, 443, 283, 392, 11, 1679

At this point, I have attempted about half the problems of LC75. I think I've chewed through most of the easy problems that I could do quickly. What remains are the sorts of problems I'll need to do more research into. I'm ready to slow down with these and change gears a little bit.

437 (partial)

437 (continued)

Even more 437.

1372, 236

199

1161, 700

450, 841

399

399, 1926, 994

547, 1466

1466

2542 (continued), 2462,

359, transcribed skiena string compare to Python

1137, 746

790

374, 2300

2300, 162, 875

215, 2336, 2542

2542

875, Reading about backtracking.