My go-to answer to the question always was backports gem: https://github.com/marcandre/backports Sadly, it is not updated for 3.2 (seems that the primary maintainer is not very active online lately), but I actually plan to provide the PR in some upcoming weeks. Another option to look into is polyfils/transpiler gem https://github.com/ruby-next/ruby-next... which isn't updated for 3.2 either :( V. чт, 29 груд. 2022 р. о 19:45 Eustáquio Rangel via ruby-core < ruby-core@ml.ruby-lang.org> пише:
I was wondering that every piece of code (gems, etc) that use the new Data object from now on will demand a mandatory upgrade to >= 3.2.0. It's a good thing upgrade the language versions, but often we can't do it for many reasons and would love to use the new code (updated or new gems) on our projects current versions.
On the original Data PR I saw one of the reasons asking Data be a language feature and not a gem ("nobody will even try to use a gem for representing it with, unless the framework/library used already provides one"), I agree with that, but I'm curious if i there is any plan to support older language versions, like releasing a gem to mimic main Data features into older language versions and not force a mandatory upgrade to >= 3.2.0. I searched on rubygems but didn't find one like that.
Btw, looks like what we had before with Fibers and Ractors, but seems to me Data will have an easier and faster adoption.
Thanks. ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org...