01:08 <FromGitter> <mattrberry> ```a = 1 ⏎ puts typeof(a) ⏎ spawn { a = "string" }``` ⏎ ⏎ This example prints `(Int32 | String)`. I don't know much about crystal fibers. I figure the compiler *could* track that the main fiber never yields here so the spawned channel will never run. I'm guessing that's just not worth the overhead of tracking at compile-time for silly examples like this? [http

01:08 <FromGitter> ... s://gitter.im/crystal-lang/crystal?at=62a7df90deea5616bbf77366]

01:09 <FromGitter> <Blacksmoke16> Is it because it creates a closure

01:09 <FromGitter> <Blacksmoke16> Like try it with a proc that you don't call

01:12 <FromGitter> <mattrberry> Yeah that's surprising too

01:13 <FromGitter> <mattrberry> I imagine typeof(a) should print Int32 since there's no way for it to be a string at that point

01:13 <FromGitter> <mattrberry> It behaves the same way as above with a proc, as you suggested

01:14 <FromGitter> <mattrberry> I'll open a github issue just to gather thoughts

01:19 <FromGitter> <naqvis> `typeof` is a runtime thing, if you need compile time value, use `puts a.class` instead.

01:19 <FromGitter> <Blacksmoke16> It's the opposite ^

01:21 <FromGitter> <naqvis> https://carc.in/#/r/db35

01:22 <FromGitter> <Blacksmoke16> Right, at runtime it knows it's a number

01:23 <FromGitter> <naqvis> aahh, gotcha

01:23 <FromGitter> <naqvis> `typeof` is a pseudo-method

01:23 <FromGitter> <Blacksmoke16> Ye

01:23 <FromGitter> <naqvis> 🌹

02:10 <FromGitter> <mattrberry> I'd like to make a unique Bytes-like type that adds some additional methods. Is that possible? For example, I'd like to have a Slice(UInt8) that adds a method to interpret the first few bytes a certain way

02:11 <FromGitter> <naqvis> You can wrap Bytes inside your custom class

02:12 <FromGitter> <naqvis> and delegate bytes related methods to bytes obj you wrapped

02:13 <FromGitter> <mattrberry> Thanks, that's what I just did 👍

02:14 <FromGitter> <naqvis> 👍

18:17 <renich> @Blacksmoke16: man Chapter 3 has an error in the Location struct for the building instance. It says 'p store' at the end. I think you meant 'p building'. Page 84 in the pdf.

18:17 <FromGitter> <Blacksmoke16> 😱

18:29 <FromGitter> <Blacksmoke16> That was one of @lbguilherme's chapters. Not sure how they handle edits tho?

18:41 <renich> @Blacksmoke16: OK, just wanted to report it.

18:43 <FromGitter> <Blacksmoke16> 👍 thnaks

18:56 <analogsalad> Blacksmoke16: Probably here? https://www.packtpub.com/submiterrata

18:58 <FromGitter> <Blacksmoke16> oh perfect yea

18:58 <analogsalad> I was wondering why I haven't noticed it, turns out I'm on page 81- 3 more pages to go.

19:01 <analogsalad> Though I do have a note from that chapter I want to run by you.

19:01 <FromGitter> <Blacksmoke16> not super familiar with the specifics of it, but ill do what i can

19:02 <analogsalad> There's an example where a class is reopened to add a new method. It's said "when reopening a class, it's parent class should not be specified."

19:03 <analogsalad> This made me think that specifying the parent class would cause a compiler error, rather than it's just redudant.

19:03 <analogsalad> *redundant.

19:04 <FromGitter> <Blacksmoke16> it might just be to prevent issues with changes in the hierarchy of that type

19:04 <FromGitter> <Blacksmoke16> i.e. some refactoring goes on and the parent type changes, then you'd get a compile error

19:05 <FromGitter> <Blacksmoke16> granted that assumes that happened in a way that didnt also break what you were overriding

19:05 <analogsalad> That's a good point.