04:03 <FromGitter> <newtonapple> Is there a better way to define generic types without tying them to a class or a module?

04:04 <FromGitter> <newtonapple> For example: ⏎ ⏎ ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=5b98903731a5505e0c766fbe]

04:05 <FromGitter> <newtonapple> it's not very nice to have to keep repeating the types K1,V1...

04:06 <FromGitter> <newtonapple> Furthermore, I think they are only relevant to the individual properties (params1 & params2), it feels a little odd to force the types at the class level.

04:09 <FromGitter> <newtonapple> I think something along this line makes more sense? ⏎ ⏎ ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=5b989186488f837cbcd2ab5a]

04:10 <FromGitter> <newtonapple> What do you guys think?

04:11 <FromGitter> <newtonapple> You can currently do this with methods, but not properties.

04:11 <FromGitter> <newtonapple> Maybe there is already a way to do this that I'm not aware of?

05:09 <dancrew32> brew install crystal taking quite a while (>30 mins): https://paste.pound-python.org/raw/agdDou8j8PgF8Ojm6X7u/ Any ideas?

05:48 <dancrew32> oh lol. because it is `brew install crystal-lang` :facepalm: have a good one!

06:18 <FromGitter> <bew> dancrew32 it's the same

06:19 <FromGitter> <bew> @newtonapple no way to do that, no

06:20 <FromGitter> <newtonapple> Ok

08:58 <JesseH> How do I access ENV from an ECR template?

09:06 <FromGitter> <straight-shoota> JesseH: `ENV["myenvvar"]`?

09:29 <JesseH> I'm silly. I used parentheses instead of brackets and it was confusing. Hard to notice sometimes as I skim over errors pretty fast by habit. Thanks, FromGitter!

09:29 <FromGitter> JesseH, I'm a bot, *bleep, bloop*. I relay messages between here and https://gitter.im/crystal-lang/crystal

09:29 <JesseH> I mean straight-shoota*

09:50 <livcd> looks like truffleruby wont support Windows anytime soon

09:51 <FromGitter> <drum445> Thanks for fixing this issue guys: https://github.com/crystal-lang/crystal/issues/6405

13:13 <FromGitter> <epergo> what do you folks think about having mandatory type declaration in class attributes? (instance variables macros)

13:14 <FromGitter> <epergo> I mean, why should this ⏎ ⏎ ```property my_property``` ⏎ ⏎ be allowed, if later you have to specify it somewhere? like initialize params [https://gitter.im/crystal-lang/crystal?at=5b9911261e2b442a25ff4dab]

13:15 <FromGitter> <epergo> shouldn't be better to have mandatory types in `property` , `getter`, etc? that way we could remove a bit (just a bit) of code from object macros, parser and hopefully resolve types of instance variables a bit sooner

13:16 <FromGitter> <epergo> I was reading https://github.com/crystal-lang/crystal/issues/4864 and I think this should be revisited and just remove some features for better maintainability/performance of the compiler

13:17 <FromGitter> <epergo> as always my 2cents

13:46 <FromGitter> <bararchy> Wooooot https://github.com/ysbaddaden/muco

13:46 <FromGitter> <j8r> this remind me Go

13:47 <FromGitter> <j8r> @epergo the response is on the issue you posted, the types are mandatory now because else it was leading to poor performance

13:49 <FromGitter> <j8r> because type inference isn't free, there is some copy for all available types something in this essence, don't know the exact details

13:57 <FromGitter> <bararchy> yeha @j8r, it's the same idea i guess, now let's see if this can be used in Crystal ;)

15:09 <FromGitter> <kolyaio> .Hey! ⏎ ⏎ I'm trying to install sentry but during the installation it prints out the following error. ⏎ ⏎ It's seems like some compiling error. ... [https://gitter.im/crystal-lang/crystal?at=5b992c22a04db554a715e73e]

16:07 <FromGitter> <bew> Do you have the same error without using --release ?

17:24 <FromGitter> <mikejohnduran> Hey everyone, are there currently any better resources/documentations for Crystal? Ideally, I am looking for a list of all Crystal methods, something such as this ruby command in the terminal ( "strings".methods or Integer.methods)

17:27 <FromGitter> <bew> There's the api documentation online

17:42 <FromGitter> <mikejohnduran> Thank you, I'll take a look at it. So far it seems to have the information I am looking for

18:24 <FromGitter> <kolyaio> @bew ⏎ Sorry it should be like that the 2nd error: ⏎ ⏎ ```bash $ crystal build --release dev/sentry_cli.cr -o ./sentry ``` ⏎ ... [https://gitter.im/crystal-lang/crystal?at=5b9959cb7189ae6fddb5b1ab]

18:31 <FromGitter> <fridgerator> is it the LLVM version?

18:38 <FromGitter> <chunkbin> Is there a debugger available for Crystal yet?

18:39 <FromGitter> <Grabli66> Hi! Anyone know how to set output path for target in shards.yml?

19:04 <FromGitter> <r00ster91> Can I call it a bug when I always get this warning: ⏎ ⏎ ```code paste, see link``` ⏎ ⏎ even if I'm not doing any GC stuff myself in my code? [https://gitter.im/crystal-lang/crystal?at=5b996329a56b215c972adb50]

19:10 <FromGitter> <r00ster91> Never mind I figured it out

19:36 <FromGitter> <bararchy> @r00ster91 it's just a GC warning, try and do less alocations, or, just ignore this message if it doesn't make sense

19:37 <FromGitter> <bararchy> it does it alot when you use stuff like ⏎ ⏎ ```.each do |ex| ⏎ array << object ⏎ end ⏎ ``` [https://gitter.im/crystal-lang/crystal?at=5b996af8fcba1254faa7a5a1]

19:37 <FromGitter> <bararchy> etc..

19:50 <FromGitter> <vladfaust> Not sure if a bug. https://carc.in/#/r/4ych compiles, but https://carc.in/#/r/4yci does not

20:00 <robacarp> that's not a bug. the two macro blocks each have their own scope, so macro varables aren't shared. Wrapping them in begin/end blocks is the right way around that.

21:27 <FromGitter> <vladfaust> alright

21:49 <FromGitter> <jwoertink> What's the sentiment on housekeeping like on this PR? https://github.com/crystal-lang/crystal/pull/4056 I don't want to be that annoying guy pinging everyone "hey, did you forget about this?" However, maybe they forgot about that lol

21:50 <FromGitter> <jwoertink> There's some old issues requesting changes, or some that are approved, but old. Is there anyone that goes back through these old issues to see if those requested changes can still be made or else close the PR?