00:40 <FromGitter> <HertzDevil> what's the difference between `Type#covariant?` and `Type#implements?`

00:40 <FromGitter> <HertzDevil> (in the compiler)

11:30 <FromGitter> <asterite> @HertzDevil I can't remember. Maybe they are the same, or they are slightly different. The easiest thing would be to make one call the other and see what specs fail. In any case, the `Type` type has too many methods and most of them are very confusing.

16:38 <FromGitter> <asterite> It's probably different for procs

18:28 <FromGitter> <void-witch> this regex works perfectly in regex101, why does it not match anything in crystal? ⏎ ⏎ ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=604bb2d095e23446e42e24c4]

18:32 <FromGitter> <Blacksmoke16> `\#`

18:33 <FromGitter> <Blacksmoke16> actually sec

18:34 <FromGitter> <Blacksmoke16> https://play.crystal-lang.org/#/r/ajc7 this works

18:37 <FromGitter> <Blacksmoke16> i would have thought passing in the enum member manually would have the same effect tho

18:38 <FromGitter> <void-witch> huh, really? that's weird

18:42 <FromGitter> <Blacksmoke16> to be clear go to edit view, the `/m` apparently doesnt show up otherwise

18:47 <FromGitter> <void-witch> why is it matching the whole string? it should only be matching a line

18:47 <FromGitter> <void-witch> (at least, that's what it does on regex101's pcre tester)

18:55 <FromGitter> <oprypin:matrix.org> @void-witch: crystal has different meanings of flags. multiline is dotall+multiline for whatever reason

18:56 <FromGitter> <void-witch> so, how do i not do that?

18:57 <FromGitter> <oprypin:matrix.org> @void-witch: use `[^\n]` not `.`

18:57 <FromGitter> <void-witch> thanks! i also just solved it by changing the end to `.+?$`

18:58 <FromGitter> <oprypin:matrix.org> not the strongest solution

18:59 <FromGitter> <oprypin:matrix.org> here in particular it's fully reliable but not always applicable

19:01 <FromGitter> <void-witch> i actually ran into issues with it on the full text, your solution works perfectly tho. ty!

22:46 <FromGitter> <MrSorcus> Hi.

22:50 <FromGitter> <MrSorcus> https://gist.github.com/MrSorcus/23d5c85b7ba2232b40832f0ce39d8625 ⏎ Here is a pseudo-code, where `parse_data` must check headers, before parsing other data... ⏎ But i think about using a `spec` from stdlib for this checks 😆 ⏎ https://gist.github.com/MrSorcus/8fd7584699c0d5951d9e3e68345f74aa - like this. ⏎ It's ok to use `spec` in that way? [https://gitter.im/c

22:50 <FromGitter> ... rystal-lang/crystal?at=604bf02c5d0bfb4e58a60caf]

22:51 <FromGitter> <js:nil.im> Are there any attempts to get Crystal into distributions? I noticed it's not even in Fedora.

22:51 <FromGitter> <Blacksmoke16> Not really. What should happen if they aren't equal?

22:52 <FromGitter> <Blacksmoke16> But is there a reason you can't use HTTP::Headers?

22:53 <FromGitter> <MrSorcus> > Not really. What should happen if they aren't equal? ⏎ ⏎ Then program must exit. It's a parser for html tables. 😆

22:54 <FromGitter> <Blacksmoke16> would be better off with what you're doing in the first example. Maybe even using `ArgumentError.new` or something

22:56 <FromGitter> <MrSorcus> Ok, got it. 😉

23:42 <FromGitter> <HertzDevil> @asterite ci is green except for alpine if i simply replace `covariant?` with `implements?` lol https://github.com/HertzDevil/crystal/commit/f2aa6661e76bee213c8bda168eedbd617255310c

23:46 <straight-shoota> o_o

23:47 <FromGitter> <MrSorcus> 😆

23:51 <FromGitter> <HertzDevil> the only two places that use `Type#covariant?` are when checking abstract def arg restrictions and when checking `Proc#call`'s arguments