gravitystorm left a comment (openstreetmap/openstreetmap-website#5932)
Thanks @tomhughes , merged.
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
`--enable=frozen_string_literal` 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.
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.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5932#issuecomment-3303327967
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5932/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
