I took a journey into the heart of Ruby to learn the secrets of the /o regex modifier, and I emerged wiser, but also so deeply tired. 
When you look at this class - does anything stick out to you? Any red flags?
If you run these lines - is it what you expected? It definitely was _not_ what I expected!
It turns out the tiny /o modifier has an outside influence on how your program runs. It creates a permanent, immutable version of your regex after the _first_ time it runs. My advice now is to never use this modifier. Ever. I dig alot deeper in the article, give it a read!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
