verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
klyons has quit [Ping timeout: 264 seconds]
klyons has joined #mlpack
klyons has quit [Quit: Leaving]
JaraxussTong has quit [Quit: No Ping reply in 180 seconds.]
JaraxussTong has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#336 (master - c3b6a9b : ryan): The build passed.
travis-ci has left #mlpack []
benchmark has joined #mlpack
benchmark has quit [Client Quit]
klyons has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#337 (master - 9bd2063 : ryan): The build was broken.
travis-ci has left #mlpack []
kirizaki has joined #mlpack
< kirizaki> hi, I'm testing timer class
< kirizaki> and there is that information
< kirizaki> Note: Undefined behavior will occur if a timer is started twice
< kirizaki> so i did It
< kirizaki> and it looks like timer's counter is full
< kirizaki> screen shot
< kirizaki> I will take a look under the mask of timer class and maybe try to do something to prevent this situation?
< kirizaki> or maybe someone already did it?
benchmark has joined #mlpack
benchmark has quit [Client Quit]
klyons has quit [Ping timeout: 260 seconds]
< rcurtin> kirizaki: nobody's ever tried to improve upon that undefined behavior
< rcurtin> it seems to me that if an exception was thrown if you tried to start a timer twice (a std::invalid_argument or something, std::runtime_error maybe), that might be better than undefined behavior
klyons has joined #mlpack
klyons has quit [Ping timeout: 252 seconds]