Day 12: Hot Springs
Megathread guidelines
- Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
- Code block support is not fully rolled out yet but likely will be in the middle of the event. Try to share solutions as both code blocks and using something such as https://topaz.github.io/paste/ , pastebin, or github (code blocks to future proof it for when 0.19 comes out and since code blocks currently function in some apps and some instances as well if they are running a 0.19 beta)
FAQ
- What is this?: Here is a post with a large amount of details: https://programming.dev/post/6637268
- Where do I participate?: https://adventofcode.com/
- Is there a leaderboard for the community?: We have a programming.dev leaderboard with the info on how to join in this post: https://programming.dev/post/6631465
🔒 Thread is locked until there’s at least 100 2 star entries on the global leaderboard
🔓 Unlocked after 25 mins
T counts the number of ways to place the blocks with lengths specified in b in the remaining a.size - ai slots. If there are no more slots left, there are two cases: Either there are also no more blocks left, then everything is fine, and the current situation is 1 way to place the blocks in the slots. Otherwise, there are still blocks left, and no more space to place them in. This means the current sitution is incorrect, so we contribute 0 ways to place the blocks. This is what the
if bi >= b.size then 1L else 0Ldoes.The start at
size + 1is necessary, as we need to compute every table entry before it may get looked up. When placing the last block, we may check the entry(ai + b(bi) + 1, bi + 1), whereai + b(bi)may already equala.size(in the case where the block ends exactly at the end ofa). The+ 1in the entry is necessary, as we need to skip a slot after every block: If we looked at(ai + b(bi), bi + 1), we could start ata.size, but then, for e.g.b = [2, 3], we would consider...#####.a valid placement.Let me know if there are still things unclear :)
Thanks for the detailed explanation. It helped a lot, especially what the
tblactually holds.I’ve read your code again and I get how it works, but it still feels kinda strange that we are considering values outside of range of
aandb, and that we are marking them as correct. Like in first row of the example???.### 1,1,3, there is no spring at8and no group at3but we are marking(8,3)and(7,3)as correct. In my mind, first position that should be marked as correct is4,2, because that’s where group of 3 can fit.If you make the recurrent case a little more complicated, you can sidestep the weird base cases, but I like reducing the endpoints down to things like this that are easily implementable, even if they sound a little weird at first.
You are probably right. Just my rumblings. Thanks for the help.