<jokke>
jhass: btw: "The standard library provides a useful record macro that allows you to create immutable structs with some fields, similar to a Tuple but using names instead of indices."
<jhass>
immutable means no setters here
<jokke>
yeah, but then i don't understand why if foo.bar; foo.bar.baz is not possible
<jhass>
because you create instances that return nil for bar
<jokke>
yeah but if it's immutable and the test passes it can't be nil inside the if block
<jhass>
we had this beofre
<jhass>
*before
<jhass>
the compiler doesn't track such a property
<jhass>
it could, it's quite a bit work and a sensible thing to do after the language is stabilized
<jokke>
mmh and it's not feasible because it'd get slow, something like that?
<sdogruyol>
jhass: yeah that's also pretty welcoming :)
<jhass>
and I like that approach slightly better, "newcomer" does not have to mean "easy" but "new to the technology" and even better "new to the codebase" too
<ozra>
oh +1 on the beginner/simple/intermediate/advanced/hard flagging - will make more of us fix bugs :-)
<jhass>
newcomer issues can demand some advanced domain knowledge when they're solvable without going through an applications internals or lots of places etc.
<sdogruyol>
jhass: yeah how do you handle that ?
<jhass>
sorry?
<sdogruyol>
jhass: e.g someone might be new to the codebase but the issue domain is related to concurrency or something that's pretty specific
<sdogruyol>
jhass: how do you mark it
<jhass>
where?
<BlaXpirit>
most typically, require knowledge of how it's done in ruby >_>
<sdogruyol>
jhass: in a issue list like diaspora's
<sdogruyol>
BlaXpirit: that's also a good point
<jhass>
at diaspora I flag newcomer if it's something that touches only part of the codebase or is easy to do but gives an opportunity to learn some part of the codebase
<ozra>
perhaps #shallow #deep - for how deep into the code base you have to be knowledgable :)
<sdogruyol>
jhass: i see
<jhass>
that is if we have the orthogonal properties of complex to solve and hard to integrate, I make sure that at least one is close to zero
<jhass>
if both are low, the better
<sdogruyol>
jhass: i think i like the elixir style type: http, kind:enhancement, level: hard
<sdogruyol>
pretty descriptive from the look
<ozra>
jhass: I guess an additional "easy" flag could be added too. For issues that really are easy (and "shallow"), like doc-updating, names refactoring or the like..
<jhass>
anyway, asterite said confrontend with that idea that he wouldn't like to spare things that are quick to fix, rather have them fixed quickly than saved for somebody to get started
<jhass>
so have fun convincing him, not me
<sdogruyol>
jhass: :P
<sdogruyol>
asterite: what do you think about labeling issues like this https://github.com/elixir-lang/elixir/issues . It really makes it easier to start and descriptive from the look
<sdogruyol>
maybe i better open an issue for this :D
<crystal-gh>
[crystal] asterite pushed 1 new commit to master: http://git.io/vcbme
<crystal-gh>
crystal/master 31a61fc Ary Borenszweig: Define a simpler `Array#new` without arguments, so no checks need to be made against initial_capacity and there's no chance to raise
<travis-ci>
manastech/crystal#31a61fc (master - Define a simpler `Array#new` without arguments, so no checks need to be made against initial_capacity and there's no chance to raise): The build passed. https://travis-ci.org/manastech/crystal/builds/83932968
nakilon has joined #crystal-lang
nakilon has quit [Ping timeout: 252 seconds]
apt-get has joined #crystal-lang
<globalkeith>
ok thanks RX14
<RX14>
it's early days in terms of libraries :P
<globalkeith>
yeah it would help me prove something to my boss, i'll see if i can work with that actve_record library instead
<RX14>
well, i would love to see a clone in crystal
<globalkeith>
yes me too, using Ecto is really nice
havenwood has joined #crystal-lang
Renich has joined #crystal-lang
<jokke>
RX14: active record clone?
<jokke>
meh
<RX14>
active record implementation
<RX14>
i meant
<RX14>
i know it's not like ruby AR
<RX14>
i said active record implementation
<RX14>
ugh
<RX14>
never mind
havenwood has quit [Ping timeout: 240 seconds]
havenwood has joined #crystal-lang
<crystal-gh>
[crystal] asterite pushed 1 new commit to master: http://git.io/vcbaa
<crystal-gh>
crystal/master d661897 Ary Borenszweig: Fixed #1696: instance variable wasn't marked as nilable if assigned inside captured block or fun literal
kostya has quit [Remote host closed the connection]
havenn has joined #crystal-lang
havenwood has quit [Ping timeout: 252 seconds]
greengriminal has quit [Quit: This computer has gone to sleep]
wmoxam has quit [Quit: leaving]
wmoxam has joined #crystal-lang
globalkeith has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<crystal-gh>
[crystal] asterite pushed 1 new commit to master: http://git.io/vcNOW
<crystal-gh>
crystal/master 046154c Ary Borenszweig: Fixed #1702: "Index out of range" error when calling `.next()` on an `each_char` iterator from an empty string
sdogruyol has joined #crystal-lang
kgadek has quit [Quit: gone sleep]
havenwood has joined #crystal-lang
<travis-ci>
manastech/crystal#046154c (master - Fixed #1702: "Index out of range" error when calling `.next()` on an `each_char` iterator from an empty string): The build passed. https://travis-ci.org/manastech/crystal/builds/83963183