Description for today’s challenge is here.
The input for Day 8 looks like the following:
bearing in mind that the leading and trailing double quotes (“) are also part of the input and needs to be dealt with.
Since there are so many escape characters in the input, I decided it would be easier to put it in a text file:
and for each line, we will:
- trim the leading and trailing “
- turn the string into a list of chars
- recursively process the list, and unescaped any escaped chars (e.g. \\, \”, \x39):
What’s going on with this:
| IsEscaped (char, rest) -> …
well, that’s our super secret partial active pattern that is responsible for unescaping escaped characters:
Couple of things to note from this:
- it’s taking the entire remainder of the char list as input
- if the list is leading with \\ or \” then the unescaped \ or ” is returned alongside the rest of the list
- in the case of \x66 for example, we can take advantage of int and char conversions:
- int “0x66” will turn the hex value 66 into the corresponding integer value 102
- char 102 will return the char with the corresponding ASCII value – ‘f’
Finally, we just need to compare the total length of the raw input and the unescaped chars:
Here we need to do the reverse of what we did in Part 1, but the approach is similar – process each char, and escape \ and ” whenever we see them:
and then just compare the length of the original and the encoded version to answer the challenge:
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
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