March 2025 - ruby-talk - ml.ruby-lang.org

[ruby-talk:444644] [ANN] hoe 4.2.3 Released
by Ryan Davis 25 Mar '25

25 Mar '25

hoe version 4.2.3 has been released! * home: <http://www.zenspider.com/projects/hoe.html> * code: <https://github.com/seattlerb/hoe> * bugs: <https://github.com/seattlerb/hoe/issues> * rdoc: <http://docs.seattlerb.org/hoe/> * doco: <http://docs.seattlerb.org/hoe/Hoe.pdf> * clog: <https://github.com/seattlerb/hoe/blob/master/History.rdoc> * other: <http://github.com/jbarnette/hoe-plugin-examples> Hoe is a rake/rubygems helper for project Rakefiles. It helps you manage, maintain, and release your project and includes a dynamic plug-in system allowing for easy extensibility. Hoe ships with plug-ins for all your usual project tasks including rdoc generation, testing, packaging, deployment, and announcement. See class rdoc for help. Hint: `ri Hoe` or any of the plugins listed below. For extra goodness, see: http://docs.seattlerb.org/hoe/Hoe.pdf Changes: ### 4.2.3 / 2025-03-25 * 2 minor enhancements: * Added alias required_rubygems_version to spec. * Added clean as a prepended prerequisite to task gem.

1 0

[ruby-talk:444643] [ANN] ruby2ruby 2.5.2 Released
by Ryan Davis 25 Mar '25

25 Mar '25

ruby2ruby version 2.5.2 has been released! * home: <https://github.com/seattlerb/ruby2ruby> * rdoc: <http://docs.seattlerb.org/ruby2ruby> ruby2ruby provides a means of generating pure ruby code easily from RubyParser compatible Sexps. This makes making dynamic language processors in ruby easier than ever! Changes: ### 2.5.2 / 2025-03-25 * 1 bug fix: * Added support for 3 slot op_asgn (eg `a &= 1`)

1 0

[ruby-talk:444642] [ANN] wxRuby3 1.5.2 released
by martin＠corino.nl 22 Mar '25

22 Mar '25

This upgrade release updates the targeted wxWidgets release to the new 3.2.7 release and also provides a few updates for wxWidgets changes. ** What's Changed ** * update targeted wxWidgets release to 3.2.7 * update wxWidgets master branch compatibility to at least commit d180041641241306175ab45b685d4c54cfff0e3a For more details see the original release announcement here: https://github.com/mcorino/wxRuby3/discussions/369

1 0

[ruby-talk:444641] [ANN] minitest 5.25.5 Released
by Ryan Davis 12 Mar '25

12 Mar '25

minitest version 5.25.5 has been released! * home: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.25.5 / 2025-03-12 * 4 bug fixes: * Bumped minimum ruby to 2.7. * Fixed expectation docs for must/wont_pattern_match. (jaredcwhite) * Reorder Minitest::Test.ancestors to allow reaching Minitest::Assertions#skipped? (Edouard-chin) * Update the ruby and rails compatibility tables. (bquorning)

1 0

[ruby-talk:444640] [ANN] RubyInline 3.14.2 Released
by Ryan Davis 12 Mar '25

12 Mar '25

RubyInline version 3.14.2 has been released! * rdoc: <http://docs.seattlerb.org/RubyInline/> * home: <http://www.zenspider.com/ZSS/Products/RubyInline/> * code: <https://github.com/seattlerb/rubyinline> Inline allows you to write foreign code within your ruby code. It automatically determines if the code in question has changed and builds it only when necessary. The extensions are then automatically loaded into the class/module that defines it. You can even write extra builders that will allow you to write inlined code in any language. Use Inline::C as a template and look at Module#inline for the required API. Changes: ### 3.14.2 / 2025-03-11 * 2 bug fixes: * Fix for windows builds. (fenrir-naru) * Ruby 3.4: Fixed breakage from ruby 3.4 call stack changes.

1 0

[ruby-talk:444639] [ANN] clee-0.4.2
by ara.t.howard 09 Mar '25

09 Mar '25

*REF:* https://github.com/ahoward/clee *README.md:* NAME ---- `clee` TL;DR; -------- `clee` is a tiny, 0 dependency, DSL for building Ã¼ber clean CLIs in Ruby INSTALL ------- ```sh gem install clee ``` URI --- http://github.com/ahoward/clee ABOUT ----- `clee` is a minimalist version of `main` (https://github.com/ahoward/main) a command line DSL i wrote almost 15 years ago, that has seen over [4 million downloads](https://drawohara.io/rubygems/) > then why should i use `clee` instead of `main` ? * `clee` has 0 dependencies beyond ruby itself * `clee` is very very small ```sh drawohara@drawohara.dev:ahoward #=> loc clee/lib clee/lib/clee.rb: 478 === @loc: 478 drawohara@drawohara.dev:ahoward #=> loc main/lib main/lib/main/cast.rb: 139 main/lib/main/daemon.rb: 395 main/lib/main/dsl.rb: 65 main/lib/main/factories.rb: 24 main/lib/main/getoptlong.rb: 245 main/lib/main/logger.rb: 43 main/lib/main/mode.rb: 41 main/lib/main/parameter.rb: 589 main/lib/main/program/class_methods.rb: 362 main/lib/main/program/instance_methods.rb: 274 main/lib/main/program.rb: 6 main/lib/main/softspoken.rb: 12 main/lib/main/stdext.rb: 34 main/lib/main/test.rb: 69 main/lib/main/usage.rb: 159 main/lib/main/util.rb: 96 main/lib/main.rb: 70 === @loc: 2623 ``` * you can use this to decide which to use: ```ruby case when wants?(:simple, :tiny, :scripting) :clee when wants?(:powerful, :testable, :complete, :mature) :main else [:clee, :main].sort_by{ rand }.first end ``` API --- ##### `clee`'s api is very simple. it has every feature you need, and none that you don't, including: - auto generated help messages - support for `my_clee --help` and `my_clee help` to 'just work' - support for modifying help/usage messages simply - sane exit codes - support for --options, env=val pairs, etc - argv parsing - fancy color'd logging - modes, and sub-modes ##### the smallest clee script looks like this ```ruby require 'clee' clee do run do p 42 end end ``` ##### you can name your scripts ```ruby require 'clee' clee do run do help! #=> this will print a default usage message that will include 'my_clee' end end ``` ##### you can alter the default tldr, and help messages ```ruby require 'clee' clee do tldr <<~____ avoid using the default 'tldr' ____ end ``` ```ruby require 'clee' clee do help <<~____ NAME my_clee USAGE fully custom help... ____ end ``` ##### specifying params is trivial ```ruby require 'clee' clee do # support `my_clee --verbose` and -v # option :verbose, :v # support `my_clee --path=./lib` # option :path, value: :required # support `my_clee API_KEY=123` *and* `API_KEY=123 my_clee` # env :API_KEY # support `my_clee --foo=42` *and* `my_clee foo=42` *and* `foo=42 my_clee` syntax # param :foo, value: 'required' # the interface and help messages work the same way for all the above # def run if @options.has_key?(:verbose) @verbose = true end @path = @options.fetch(:path) @api_key = @env.fetch(:API_KEY) @foo = @parms.fetch(:foo) end end ``` ##### modes, and sub-modes, are supported ```ruby require 'clee' clee :my_clee do run :foo do p 42 end run :foo, :bar do p 42.0 end run do p 42.42 end end ``` ##### assuming you saved the above as `my_clee`, you could then do ```sh ~> my_clee foo #=> 42 ~> my_clee foo bar #=> 42.0 ~> my_clee #=> 42.42 ``` ##### `clee` scripts have a sweet dependency-less colored logger that understands what a #tty really is... ```ruby require 'clee' clee do def run log 'hai!' log 'hai!', level: :warning log 'blue', color: :blue end end ``` ##### `clee` ships with a lil code-gen-thang ```sh ~> clee new my_clee > my_clee ~> chmod 755 my_clee ~> ./my_clee ``` i could write more docs but, they would then outnumber the LOC of the library so: 1. see [./lib/clee.rb](./lib/clee.rb) 2. if that still doesn't float your boat install `ima`, a universal command-line filter built on `clee`, that brings AI to your CLI and do something like this ```sh ~> gem install clee ima ~> ima explain clee to me --context=$(gem which clee) ``` which might produce something like this -> --- Clee is a Ruby library that provides a simple way to create command-line interfaces (CLI) for Ruby applications. It allows developers to define commands, options, and parameters for their application, and handles the parsing and execution of these commands. The core features of Clee include: * Command definition: Clee allows developers to define commands and their associated options and parameters. * Option parsing: Clee can parse command-line options and parameters, and provides a simple way to define and handle these options. * Parameter handling: Clee provides a way to handle command-line parameters, including required and optional parameters. * Help generation: Clee can generate help text for commands and options, making it easy to provide documentation for users. * Logging: Clee provides a logging mechanism that allows developers to log messages at different levels (e.g. debug, info, warning, error). Clee is designed to be flexible and customizable, making it easy to integrate into existing Ruby applications. It also provides a number of features that make it easy to use, including automatic help generation and logging. Some of the key concepts in Clee include: * Commands: These are the top-level actions that a user can perform with the application. * Options: These are the flags or switches that can be used to modify the behavior of a command. * Parameters: These are the values that are passed to a command or option. * Modes: These are alternative behaviors that a command can exhibit, depending on the options or parameters passed to it. Overall, Clee is a powerful and flexible library that makes it easy to create command-line interfaces for Ruby applications. Its simple and intuitive API makes it easy to use, even for developers who are new to CLI development. --- SING IT ðŸŽµ ---------- * **DOCS are dead, long live AI!** * **UIs are dead, long live CLIS!** FINALLY ------- > why `clee`? that is honestly such a stupid name... a good friend used to pronounce 'cli' as 'clee'. it stuck. i like it. > i still need you write more docs for this free code [c'mon in!](https://github.com/ahoward/clee/pulls) -- - a "be kind whenever possible. it is always possible." -- h.h. the 14th dalai lama -->> https://drawohara.io

1 0

[ruby-talk:444635] Ruby Mixins vs Rails Concerns
by Andy Maleh 07 Mar '25

07 Mar '25

It is amazing how cryptic, difficult to reason about, and expensive to maintain Ruby codebases become when they include countless 'concerns' without honoring the Ruby naming convention for mixins as representing "traits"... Continue reading blog post: https://andymaleh.blogspot.com/2025/03/ruby-mixins-vs-rails-concerns.html

3 3