15:04 <johnjaye> hmm. when I do show_doc on Array in the irb prompt and it shows all those methods like any? or count, are those mixins from Enumerable?

15:04 <johnjaye> I ask because Array.methods - Enumerable.methods is... not a big list. so Array seems like a thin wrapper around Enumerables

15:52 <adam12> johnjaye: Yes, you've got it correct.

15:52 <johnjaye> ok

15:53 <johnjaye> the truth is revealed

16:49 <leftylink> but Array.methods tells you the methods of Array, not of an array like []. So what does `Array.methods - Enumerable.methods` really tell you? I don't think it tells you anything at all

16:50 <leftylink> wouldn't it make much more sense to group each of `[].methods` by Method#owner ?

16:51 <leftylink> you would need to turn each of the symbols (returned by #methods) into Method, but I omit obvious details

16:57 <leftylink> an example of what I mean

16:57 <leftylink> pandabot: rb class C; def foo; end end; [C.methods.include?(:foo), C.new.methods.include?(:foo)]

16:57 <pandabot> [false, true] - https://carc.in/#/r/fvtf

16:58 <leftylink> since C.methods.include?(:foo) is false, Array.methods tells you nothing.

17:18 <johnjaye> ah ok

22:29 <havenwood> johnjaye: For what it's worth, you can `Array.instance_methods(false)` or `[].public_methods(false)` to see the methods defined on Array.

22:30 <havenwood> johnjaye: If you want to know where a method is defined, you can ask it about its owner. (E.g., with `chunk` you could `[].method(:chunk).owner`.)

22:37 <havenwood> johnjaye: In irb take a look at `ls []` or `ls Array`.

23:47 <toonlink> i'm attempting to make a "custom variable assignment operator" via essentially using method_missing (i am aware it is the devil) to make undefined variable names return an object that then takes a <=> method that handles assignment. is there any way to do this that'd ensure any typos i make inside of an instance_eval actually raise errors instead of just creating a new "custom operator" object?

23:51 <johnjaye> hmm. if i do ls [] then it shows some methods marked Array and others marked Enumerable

23:51 <johnjaye> The thing is, any? is clearly an Enumerable thing but it's listed under array

23:53 <weaksauce> johnjaye any? is defined on array too

23:53 <weaksauce> so that might be why

23:54 <johnjaye> i don't follow

23:54 <weaksauce> as in they wrote extra code to define any? for array handling instead of the generic enumerable code

23:54 <johnjaye> my thought was Enumerable defines any? as an abstract thing. which array then implements

23:54 <johnjaye> hmm. wait so Enumerable defines any? as an actual function

23:54 <weaksauce> yeah a generic method

23:54 <weaksauce> https://rubyapi.org/3.2/o/array#method-i-any-3F

23:54 <johnjaye> and then Array overrode it?

23:54 <weaksauce> look at the code

23:55 <weaksauce> versus https://rubyapi.org/3.2/o/enumerable#method-i-any-3F

23:56 <johnjaye> it's the same thing

23:56 <johnjaye> return true if at least one element satisfies the block

23:56 <weaksauce> no the actual code

23:56 <weaksauce> it's both C code

23:56 <weaksauce> click on the </>

23:57 <johnjaye> the generic Enumerable takes a pattern and the array one doesn't?

23:57 <johnjaye> oh i had no idea that button did that

23:57 <johnjaye> i was confused what you were talking about.

23:58 <weaksauce> the array code also test against objects

23:58 <johnjaye> yeah it takes an object whereas the enumerable one takes a pattern

23:58 <johnjaye> meaning if i give an regexp pattern to an array.any? call it won't do what I expect?

23:59 <weaksauce> i am not sure but it seems as though they created an optimized version of array#any?