dkubb changed the topic of #datamapper to: Datamapper v1.2.0 | Mailing List: http://is.gd/aa9D | Logs: http://is.gd/qWAL7V | DataMapper 2 Renamed to ROM, see #rom-rb for development
mbj has joined #datamapper
v0n has joined #datamapper
snusnu has quit [Ping timeout: 256 seconds]
snusnu has joined #datamapper
myobie has joined #datamapper
northrup has joined #datamapper
zombor has joined #datamapper
zombor has joined #datamapper
zombor has quit [Changing host]
zombor has quit [Remote host closed the connection]
northrup has quit [Ping timeout: 276 seconds]
northrup has joined #datamapper
myobie has quit [Quit: myobie]
ckrailo has quit [Quit: Computer has gone to sleep.]
ckrailo has joined #datamapper
Sylvain1 has quit [Quit: Leaving.]
Sylvain1 has joined #datamapper
ckrailo has quit [Quit: Computer has gone to sleep.]
Sylvain1 has quit [Quit: Leaving.]
mbj has quit [Quit: leaving]
Sylvain1 has joined #datamapper
rtyler_ has joined #datamapper
Sylvain1 has joined #datamapper
rtyler has quit [Read error: Connection reset by peer]
rtyler_ is now known as rtyler
snusnu has quit [Ping timeout: 248 seconds]
snusnu has joined #datamapper
Sylvain1 has quit [Quit: Leaving.]
zombor has joined #datamapper
zombor has joined #datamapper
zombor has quit [Remote host closed the connection]
snusnu has quit [Quit: Leaving.]
Sylvain1 has joined #datamapper
<dkubb>
!memo mbj I'd like to write a mutator and assert that it *should* cause a spec failure. For example, say I come across "!!expression" and I mutate it to "expression" and run the specs, if it doesn't cause a spec failure then it's a problem because the !! are unnecessary
<Cinchy>
dkubb: Memo recorded for mbj.
<dkubb>
!memo mbj maybe the author knows it *is* necessary but chose to only write a test where expression was true or false and not 1 like it can be in real-world usage.. so it'll prompt them to fill in that case *or* remove the dead code, if that's what it is
<Cinchy>
dkubb: Memo recorded for mbj.
<dkubb>
!memo mbj we can use that to help identify other simplifications that can be made to the code using stuff like DeMorgan's Laws, eg: (not A) or (not B) -> not (A and B)
<Cinchy>
dkubb: Memo recorded for mbj.
v0n has quit [Ping timeout: 264 seconds]
knowtheory has quit [Quit: Computer has gone to sleep]
Sylvain1 has quit [Quit: Leaving.]
solnic has joined #datamapper
Sylvain1 has joined #datamapper
mbj has joined #datamapper
<mbj>
.
<Cinchy>
mbj: [2h 15m 10s ago] <dkubb> I'd like to write a mutator and assert that it *should* cause a spec failure. For example, say I come across "!!expression" and I mutate it to "expression" and run the specs, if it doesn't cause a spec failure then it's a problem because the !! are unnecessary
<Cinchy>
mbj: [2h 14m 17s ago] <dkubb> maybe the author knows it *is* necessary but chose to only write a test where expression was true or false and not 1 like it can be in real-world usage.. so it'll prompt them to fill in that case *or* remove the dead code, if that's what it is
<Cinchy>
mbj: [2h 11m 47s ago] <dkubb> we can use that to help identify other simplifications that can be made to the code using stuff like DeMorgan's Laws, eg: (not A) or (not B) -> not (A and B)
<Cinchy>
snusnu: [3h 31m 52s ago] <mbj> I have a wired crash under jruby with substation, pls reproduce, if possible: https://gist.github.com/mbj/6068670
snusnu has quit [Quit: Leaving.]
snusnu has joined #datamapper
mikecmpbll has joined #datamapper
mikecmpbll has quit [Quit: Computer has gone to sleep.]
rafaelfranca has joined #datamapper
mikecmpbll has joined #datamapper
rafaelfranca has quit [Ping timeout: 264 seconds]
rafaelfranca has joined #datamapper
rafaelfranca has quit [Remote host closed the connection]
<dkubb>
!memo mbj do you think whitequark would accept a patch to AST::Node that adds #eql? and #hash?
<Cinchy>
dkubb: Memo recorded for mbj.
gix has quit [Quit: Client exiting]
Ortuna has joined #datamapper
Ortuna has quit [Client Quit]
Ortuna has joined #datamapper
gix has joined #datamapper
v0n has quit [Read error: Operation timed out]
bobocopy1 has joined #datamapper
bobocopy has quit [Ping timeout: 246 seconds]
v0n has joined #datamapper
postmodern has joined #datamapper
gix has quit [Quit: Client exiting]
gix has joined #datamapper
mbj has joined #datamapper
<mbj>
.
<Cinchy>
mbj: [5h 6m 12s ago] <dkubb> I'd like to get your input on the mutations in https://github.com/mbj/mutant/pull/76 .. not sure if they are too aggressive or not
<Cinchy>
mbj: [1h 55m 0s ago] <dkubb> do you think whitequark would accept a patch to AST::Node that adds #eql? and #hash?
<mbj>
dkubb: Yeah I think he'd accept this.
<mbj>
dkubb: Pls keep in mind we cannot use equalizer, he plans to create an ruby implementation on top of parser and ast, so he has to minimize deps.
<dkubb>
mbj: yeah I figured that
<dkubb>
mbj: I will probably use a similar implementation to what equalizer uses
<dkubb>
it doesn't have to be generic, so I can cut out lots of code
<mbj>
dkubb: yeah
<mbj>
dkubb: I think he'll accpept such additions.
<dkubb>
cool
solnic has joined #datamapper
zombor has quit [Remote host closed the connection]
rsim has joined #datamapper
rsim has quit [Ping timeout: 240 seconds]
mbj has quit [Ping timeout: 240 seconds]
rsim has joined #datamapper
Sylvain1 has joined #datamapper
jeremyevans has quit [Ping timeout: 246 seconds]
Sylvain2 has joined #datamapper
Sylvain1 has quit [Ping timeout: 246 seconds]
lnormous has joined #datamapper
v0n has quit [Ping timeout: 240 seconds]
<lnormous>
What's the best way to handle case-insensitive uniqueness on a postgres database
<lnormous>
validates_uniqueness_of seems case-sensitive - is there an option to make it case insensitive?
bobocopy1 is now known as bobocopy
bobocopy is now known as akasper
rsim has quit [Quit: Leaving.]
rafaelfranca has quit [Remote host closed the connection]