09:59 <nakilon> can't decide, whether in all the methods where I return lists, I should return Array and let people iterate over them, or should I yield, leaving them to .to_a if they want; what should be the rule of thumb?

10:01 <nakilon> or should I even (the 3rd option) check if the block is passed?

10:02 <nakilon> that would be overengineering, so I should chose of from those two ways; do I return Array or do I yield the items?

10:16 <nakilon> hmm, I think by yielding I make two "access points" -- the value is still returned from the method and the yielded args can be from anywhere deep inside of it; so the yielding is an additional data exposing, not a replacement for the return value

13:59 <nakilon> I wish the refinement syntax was not "using M" but "M.using"

14:02 <nakilon> oh, nvm, "using" is already a method of something

14:06 <nakilon> still would be cool if I could pass an argument of what class I want to refine, instead of having its name hardcoded

14:08 <nakilon> for example, I have a module with a method, and I do "obj.extend(my_module).my_method", applying it to an obj no matter what class it belongs -- it only needs to quack a bit

14:09 <nakilon> with refinements I'm unable to do, because there after the "refine" keyword you specify what class you want to refine

14:10 <nakilon> I wish I could use the same module I use for the "extend" trick to refine all the instances of some arbitrary class in the source file

14:10 <nakilon> because the "extend" starts to be a clutter

22:52 <hd1> does ruby have translated keywords?

22:55 <mange> I'm not sure what you're asking. What are "translated keywords"?

22:56 <hd1> method names like Array.each

22:57 <hd1> if my localization is French, is Array.chaque supported?

23:02 <o0x1eef> hd1: No

23:02 <o0x1eef> That said, method names can be UTF-8

23:03 <hd1> o0x1eef: I'm aware of that

23:04 <o0x1eef> Okay. Well, there's no method names based on locale.

23:04 <mange> Are there many programming languages with localized names? Every language I can think of picks a natural language. Although https://en.wikipedia.org/wiki/Non-English-based_programming_languages lists a few with multiple translations.

23:05 <mange> Apparently there are Ruby variants translated into Latvian and Tagalog, if that helps. :P

23:05 <o0x1eef> This is probably the most famous example of a UTF-8 method name: https://github.com/sidekiq/sidekiq/blob/main/lib/sidekiq.rb#L45-L47

23:08 <o0x1eef> Good or bad, English is generally the language used in sciences. So it is worth knowing at least the basics.

23:10 <weaksauce> i'm sure you could make a gem that aliases all the methods in whatever you care about into french

23:11 <o0x1eef> I suddenly feel like a tourist in Paris

23:11 <hd1> the gem would just be a list of alias_method calls

23:12 <o0x1eef> You would probably want to assign constant names as french too

23:23 <weaksauce> yup

23:25 <o0x1eef> I'm curious, what is your use-case ? Because I think it is filled with problems. Even if you translate all the core classes, what happpens when you want to use a gem ? Is English okay then ? Or will you also translate any gem you want to use ? At that point, is it really productive not to just use English ? Ruby is Japanese but Ruby itself uses the English language. IMO that's a good indicator.