04:34 <FromGitter> <mattrberry> @oprypin The current macro language wouldn't necessarily need to be dropped in order to support compile-time evaluation from the interpreter, would it?

07:04 <FromGitter> <oprypin:matrix.org> @mattrberry: not necessarily, but can you imagine how neat it would be if the Crystal evaluation *was* a drop-in replacement for macros with only occasional changes required

13:13 <FromGitter> <moe:busyloop.net> don't let perfect be the enemy of good tho

13:15 <FromGitter> <moe:busyloop.net> i wouldn't like having rewrite all my macros. ⏎ but i would like not having to write any new ones.

13:16 <FromGitter> <spuun> @moe:busyloop.net please create a github issue for your cross compiling issues with 84codes images

13:20 <FromGitter> <moe:busyloop.net> @spuun: i've added a note to the existing ticket: https://github.com/crystal-lang/crystal/issues/11703#issuecomment-1268425614

13:20 <FromGitter> <spuun> @moe:busyloop.net ah, great!

13:21 <FromGitter> <spuun> @moe:busyloop.net but maybe create an issue on https://github.com/84codes/crystal-container-images too? so we can fix our images

13:22 <FromGitter> <moe:busyloop.net> roger, will do. (wanted to do that anyway but then got distracted by something else)

13:22 <FromGitter> <spuun> :)

13:25 <FromGitter> <moe:busyloop.net> done

13:25 <FromGitter> <moe:busyloop.net> would be superduper to have this fixed, rsync'ing my stuff to a linux box to compile is a bit annoying 😓

13:28 <FromGitter> <moe:busyloop.net> aaaand closed, lol

13:29 <FromGitter> <spuun> Great! haha :D

13:32 <FromGitter> <moe:busyloop.net> thanks 🙇 ⏎ i keep forgetting about the entrypoint stuff.

13:33 <FromGitter> <spuun> victory! :)

18:59 <yujiri> Hi, how can I get a slice from an array?

19:07 <FromGitter> <Blacksmoke16> Think you could do something like: ⏎ ⏎ ```Slice.new array.to_unsafe, array.size``` [https://gitter.im/crystal-lang/crystal?at=633dd5f9683a5c58c7201fc0]

19:11 <yujiri> thanks