08:32 <mikko> just to check, am i doing something stupid if i use "Benchmark.measure { Process.run(cmd, input: io_in, output: io_out) }" to time external processes?

08:33 <mikko> both io_in and io_out are IO::Memory objects

08:36 <mikko> feels like it might be measuring stuff i don't really care about, like passing those IO objects to Process.run, but i'm not sure how i would ever know if there is enough overhead for it to matter

12:38 <FromGitter> <Blacksmoke16> What are you actually wanting to benchmark?

14:40 <FromGitter> <y8> Hi! Is there nightlies of macos-arm64 somewhere?

19:39 <FromGitter> <oz:matrix.org> Not yet.

20:32 <hightower3> So what's a good way to produce a "pointer" to a method? (something other than ->method(...), given that that only works with methods that don't have required named params)

20:33 <FromGitter> <Blacksmoke16> make another method that doesnt use named args and delegates to the other ? :P

20:33 <hightower3> and @[AlwaysInline] it ;-) sure, when it's a party...

20:34 <FromGitter> <Blacksmoke16> however i will say, not sure if its a bug or intended that it doesnt work with named args

20:35 <FromGitter> <Blacksmoke16> might be worth filing an issue for (or at least searching first)

20:35 <hightower3> will do, thank you kindly

20:35 <hightower3> there is also https://github.com/wyhaines/Send.cr that was demoed during Crystal conf, although it's not exactly what I need in this case

20:43 <hightower3> It seems that https://github.com/crystal-lang/crystal/issues/560 and https://github.com/crystal-lang/crystal/issues/1064 have at least remotely something to do with this particular point

20:44 <hightower3> but I didn't find anything directly related to -> and named args

20:44 <hightower3> will open a ticket

20:53 <hightower3> https://github.com/crystal-lang/crystal/issues/11099

22:00 <FromGitter> <nanobowers> Is there a guide on what to do when i get one of these backtraces? ⏎ ⏎ ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=611ae00209a1c273827e26ef]

22:00 <FromGitter> <Blacksmoke16> Oof

22:00 <FromGitter> <nanobowers> output truncated, there was more

22:02 <FromGitter> <Blacksmoke16> Best bet would be try and reduse it as much as you can to figure out the root cause

22:34 <FromGitter> <nanobowers> I *think* i accidentally did it by calling `super()`, instead of `super` or `super(a,b,c...)` which seems to compile fine, but i can only assume that super() is calling all the way back to Object#initialize and not setting any of the instance variables that the superclass wouldve been setting had I actually been calling that super

22:34 <FromGitter> <Blacksmoke16> that would make sense

22:36 <FromGitter> <Blacksmoke16> well no, test i did i get an error because of no overload

22:37 <FromGitter> <Blacksmoke16> id still try and get a minimally reproducing program