home.social

#frozenstring — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #frozenstring, aggregated by home.social.

  1. Just ran across this gem from @palkan at @evilmartians. I detest #frozenstring literals, think default #RuboCop is on crack, and am unconvinced that String reuse is always better than being GC-able.

    #Standardrb is less painful than RuboCop's defaults. Now add #Freezolite to solve problems around frozen strings in a sane, tunable, and project-wide way rather than at the file or interpreter level. It allows for inclusions & exclusions, making it fit more use cases IMHO.

    github.com/ruby-next/freezolit

  2. Just ran across this gem from @palkan at @evilmartians. I detest #frozenstring literals, think default #RuboCop is on crack, and am unconvinced that String reuse is always better than being GC-able.

    #Standardrb is less painful than RuboCop's defaults. Now add #Freezolite to solve problems around frozen strings in a sane, tunable, and project-wide way rather than at the file or interpreter level. It allows for inclusions & exclusions, making it fit more use cases IMHO.

    github.com/ruby-next/freezolit

  3. Just ran across this gem from @palkan at @evilmartians. I detest #frozenstring literals, think default #RuboCop is on crack, and am unconvinced that String reuse is always better than being GC-able.

    #Standardrb is less painful than RuboCop's defaults. Now add #Freezolite to solve problems around frozen strings in a sane, tunable, and project-wide way rather than at the file or interpreter level. It allows for inclusions & exclusions, making it fit more use cases IMHO.

    github.com/ruby-next/freezolit

  4. Just ran across this gem from @palkan at @evilmartians. I detest #frozenstring literals, think default #RuboCop is on crack, and am unconvinced that String reuse is always better than being GC-able.

    #Standardrb is less painful than RuboCop's defaults. Now add #Freezolite to solve problems around frozen strings in a sane, tunable, and project-wide way rather than at the file or interpreter level. It allows for inclusions & exclusions, making it fit more use cases IMHO.

    github.com/ruby-next/freezolit

  5. Just ran across this gem from @palkan at @evilmartians. I detest #frozenstring literals, think default #RuboCop is on crack, and am unconvinced that String reuse is always better than being GC-able.

    #Standardrb is less painful than RuboCop's defaults. Now add #Freezolite to solve problems around frozen strings in a sane, tunable, and project-wide way rather than at the file or interpreter level. It allows for inclusions & exclusions, making it fit more use cases IMHO.

    github.com/ruby-next/freezolit