<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with standardrb]]></title><description><![CDATA[A list of topics that have been tagged with standardrb]]></description><link>https://board.circlewithadot.net/tags/standardrb</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 07:06:24 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/standardrb.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Another rubocop&#x2F;standardrb gripe:]]></title><description><![CDATA[@soulcutter I don’t think it would. Most JITs do not apply much optimization just translate to native code. Parser applies some optimizations when generating bytecode though. There are some specialized ops in bytecode, too.]]></description><link>https://board.circlewithadot.net/topic/80513f0f-9051-43b9-b52d-e587f5519aa2/another-rubocop-standardrb-gripe</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/80513f0f-9051-43b9-b52d-e587f5519aa2/another-rubocop-standardrb-gripe</guid><dc:creator><![CDATA[pointlessone@status.pointless.one]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>