Description for today’s challenge is here.
First, let’s define the 6 instructions on the computer:
and parse the input file (see example below) into the DU type above
jio a, +16
Then we add a function to iterate through the instructions, a simple (tail) recursive loop function would do the trick. The below should be pretty self-explanatory, two tricky things to keep in mind:
- that jio stood for “jump if one” rather than the more intuitive “jump if odd” given that jie is “jump if even”…
- the problem specifies the register value to be non-negative, and just in case we’ll overflow, use an unsigned long
and all that’s left is to call the function with the instructions we have parsed from the input and ask for the value of the b register at the end.
For Part 2, we just need to change the initial register values we pass into the loop:
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong