<div style="display: flex; flex-wrap: wrap; white-space: pre-wrap; align-items: center; "><img height="20" width="20" style="border-radius:50%; margin-right: 4px;" decoding="async" src="https://avatars.githubusercontent.com/u/360803?s=20&v=4" /><strong>gravitystorm</strong> left a comment <a href="https://github.com/openstreetmap/openstreetmap-website/pull/5932#issuecomment-3303327967">(openstreetmap/openstreetmap-website#5932)</a></div>
<p dir="auto">Thanks <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/tomhughes/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/tomhughes">@tomhughes</a> , merged.</p>
<p dir="auto">I've been trying to avoid making changes to 800+ files since the whole frozen-string thing was first mentioned in the ruby2.x era, hoping that we could find a different approach. However, I can't see a better alternative now that ruby 3.4 is generating copious warnings. If all our deps were safe (which they aren't) and if there was a straightfoward way to pass the <code class="notranslate">--enable=frozen_string_literal</code> option to just affected versions of ruby (i.e. 3.4+) for every possible way a dev might try to run our code (which there isn't), then I would have chosen that instead.</p>
<p dir="auto">I'm already looking forward to removing these pragmas at some point in due course! Here's hoping that upstream ruby don't make the transition drag out for too much longer.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/5932#issuecomment-3303327967">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLI6JCIRFQLPXH226F33TFXCPAVCNFSM6AAAAAB3FAXKZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBTGMZDOOJWG4">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLKLUDUADQ3WJ3B66X33TFXCPA5CNFSM6AAAAAB3FAXKZCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWE4TEN6.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/pull/5932/c3303327967</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>

<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/pull/5932#issuecomment-3303327967",
"url": "https://github.com/openstreetmap/openstreetmap-website/pull/5932#issuecomment-3303327967",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>