tomchapin has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dylanmei has quit [Quit: ZZZzzz…]
fowlduck has joined #crystal-lang
x0f has quit [Ping timeout: 250 seconds]
dylanmei has joined #crystal-lang
x0f has joined #crystal-lang
dylanmei has quit [Quit: ZZZzzz…]
dylanmei has joined #crystal-lang
Philpax has quit [Ping timeout: 256 seconds]
dylanmei has quit [Quit: ZZZzzz…]
dylanmei has joined #crystal-lang
dylanmei has quit [Quit: ZZZzzz…]
fowlduck has quit [Remote host closed the connection]
toydestroyer has quit [K-Lined]
toydestroyer has joined #crystal-lang
<crystal-gh>
[crystal] asterite pushed 3 new commits to master: https://git.io/vzwDE
<crystal-gh>
crystal/master d9e7db4 Ary Borenszweig: Added docs for the new `HTTP::Server`
<crystal-gh>
crystal/master 9952874 Ary Borenszweig: Renamed `HTTP::WebSocketSession` to `HTTP::WebSocket` and `HTTP::WebSocket` to `HTTP::WebSocket::Protocol`
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Philpax has quit [Ping timeout: 256 seconds]
nakilon has joined #crystal-lang
dylanmei has joined #crystal-lang
fowlduck has joined #crystal-lang
fowlduck has quit [Ping timeout: 260 seconds]
trapped has joined #crystal-lang
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
fowlduck has joined #crystal-lang
nakilon has quit [Quit: WHY NOT?]
ytti has joined #crystal-lang
<ytti>
is there standard lib way to recover hostname, domainname, os runtime?
<ytti>
i could just Process#run uname, i guess
trapped has joined #crystal-lang
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
trapped has joined #crystal-lang
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
trapped has joined #crystal-lang
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<crystal-gh>
[crystal] asterite pushed 1 new commit to master: https://git.io/vzrVB
<crystal-gh>
crystal/master ed88d5f Ary Borenszweig: Removed the browser tool
trapped has joined #crystal-lang
fowlduck has quit [Remote host closed the connection]
krtv` has joined #crystal-lang
buggs has joined #crystal-lang
fowlduck has joined #crystal-lang
<chrisseaton>
Hi - does &block work the same way in Crystal as in Ruby? I have '@pairs.get_one { | p | p.key == key }', defined as 'def get_one(&block)' and am told 'wrong number of block arguments (1 for 0)'
<asterite>
chrisseaton: if the block isn't captured, it works the same as in Ruby. That could shouldn't be giving you that error, what's the full code?
<asterite>
Now, if you use `block.call`, right now the compiler assumes the block is captured (even if you don't pass it around), and there the number of arguments is checked
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
shama has joined #crystal-lang
triangles has joined #crystal-lang
<ytti>
i still can't get my mind over how dynamic crystal feels
<ytti>
very very rare that i have to fix something with types
<ytti>
just too many 'new' interesting languages, rust, crystal, swift, go
<ytti>
elixir
shama has quit [Remote host closed the connection]
<dom96>
ytti: don't forget Nim ;)
<ytti>
i'm not really interested in nim
<ytti>
i don't know why, but it rubs me the wrong way that it uses C as interim
fowlduck has quit [Remote host closed the connection]
trapped has joined #crystal-lang
fowlduck has joined #crystal-lang
trapped has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
fowlduck has quit [Ping timeout: 260 seconds]
shama has joined #crystal-lang
trapped has joined #crystal-lang
shama has quit [Ping timeout: 250 seconds]
fowlduck has joined #crystal-lang
<dom96>
ytti: that's the first time I ever heard anyone have a negative reaction to a programming language using C as a compilation target. In my experience it works very well. Is there anything in particular about it that discourages you from the idea?
<ytti>
dom96, no, it's just completely emotion based judgement
<ytti>
i have unjustfied amount of dislike for c
shama has joined #crystal-lang
<chrisseaton>
What should I do about a '(isValidElementType(EltTy) && "Invalid type for pointer element!")' error?
<chrisseaton>
There's not much information to even indicate where the problem might be?
<dom96>
ytti: That's fair enough. But keep in mind that you can use Nim perfectly well without caring about the fact that it compiles to C at all.
<asterite>
chrisseaton: `until x` is rewritten as `while !x`, and right now `!` doesn't restrict types. Another way to write `until foo.is_a?(Nil)` is `while foo`, you can use that
<asterite>
chrisseaton: and the last error is an LLVM assertion triggering, so a compiler bug
<chrisseaton>
asterite: ok thanks I'll file an issue
greengriminal has joined #crystal-lang
trapped has quit [Read error: Connection reset by peer]
trapped has joined #crystal-lang
Philpax has joined #crystal-lang
shama has quit [Remote host closed the connection]
<CompanionCube>
ytti, the language will be requiring more type annotations soon
<CompanionCube>
for instance & class variables
<ytti>
i'm cool with that
<ytti>
of course for crystal developers it must be scary
<ytti>
because it's hard decision, do you risk the traction you already have, or do you accept the language isn't exactly what you want it to be
<ytti>
at some point in language's life, the latter thing must be accepted, you can't do major changes anymore, as it'll just kill traction and people will find it less hassle to evaluate all the available options, instead of new slightly diffferent version of current language
<ytti>
i'm all for breaking backward compatibility in effort of trying to produce the result which I think is best
<ytti>
but i fully understand how it will alienate userbase
<CompanionCube>
you will see my opinions on the issue as @samis