02:13 <FromGitter> <andrewc910> Why are some variables in shards/gems prepended with an underscore? What does it represent? Like `@_broadcast_handlers`. The author of Jennifer also does this quite a bit.

02:19 <FromGitter> <Blacksmoke16> it is/was a common practice in some langs to denote it as private or internal

03:35 <FromGitter> <andrewc910> That's what it looked like. Thank you

03:52 <FromGitter> <Blacksmoke16> no

03:52 <FromGitter> <Blacksmoke16> np

08:08 <FromGitter> <confact> Before Kindmetrics I was doing a git hosting service to learn git deep depth but also Crystal and Lucky. Now I have made it open source as I lost a bit of motivation and would love to give it some life again. Would love any help I can get on it :) ⏎ ⏎ https://github.com/microgit-com/microgit

11:27 <FromGitter> <lbarasti> puzzled by the behaviour of OpenSSL::Sha1 ⏎ ⏎ ```code paste, see link``` ⏎ ⏎ which prints two different slices: https://play.crystal-lang.org/#/r/9el2 [https://gitter.im/crystal-lang/crystal?at=5f09a22df6b741628429a355]

11:29 <FromGitter> <lbarasti> does this have to do with the fact that SHA1.hash uses `uninitialized UInt8[20]`?https://github.com/crystal-lang/crystal/blob/5999ae29beacf4cfd54e232ca83c1a46b79f26a5/src/openssl/sha1.cr#L10

11:29 <FromGitter> <lbarasti> https://github.com/crystal-lang/crystal/blob/5999ae29beacf4cfd54e232ca83c1a46b79f26a5/src/openssl/sha1.cr#L10

11:31 <FromGitter> <lbarasti> removing `.slice` or adding `.dup` fixes the inconsistency

11:37 <oprypin> lbarasti, i think there were isses brought up many many times that `StaticArray#to_slice` is very very unsafe and should be clearly marked as such

11:37 <oprypin> staticarray resides on the stack and as soon as you exit the scope the memory is not reserved to it anymore . but the slice keeps pointing to the same memory

11:39 <FromGitter> <lbarasti> ouch! Thanks oprypin, good to narrow down the issue to `StaticArray#to_slice`, I can now go and remove a bunch of unnecessary `.dup` :D

11:41 <FromGitter> <asterite> we should probably rename it to to_unsafe_slice

16:13 <FromGitter> <jwaldrip> Why would this be possible? ⏎ ⏎ ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=5f09e52e3e4a827d19bc76a2]

16:17 <FromGitter> <Blacksmoke16> prob typing

16:18 <FromGitter> <Blacksmoke16> `acc` and `val` prob get set to a union of the possible types in the array which messes things up

16:29 <FromGitter> <asterite> this is your daily reminder to not use named tuples

17:48 <FromGitter> <kingsleyh> What’s the deal with names Tuples

18:27 <FromGitter> <straight-shoota> > this is your daily reminder to not use named tuples ⏎ ⏎ @asterite Made my day =)

19:18 <FromGitter> <asterite> they represent named arguments. That's all. If you are using them for something else, you are using them in the wrong way, and it's almost guaranteed you'll have a bad time unless you use them for the simplest things

19:57 <FromGitter> <straight-shoota> Bottom line: For every use case of named tuples except named arguments, it's better to use structs

20:17 <yxhuvud> often in the form of Records.