oznek_ has quit [Remote host closed the connection]
Munto has quit [Quit: Leaving]
grenierm has joined #ruby
Sheilong has quit [Quit: Connection closed for inactivity]
schne1der has joined #ruby
wbooze has joined #ruby
Artea has quit [Ping timeout: 252 seconds]
Artea has joined #ruby
infinityfye has joined #ruby
TomyWork has joined #ruby
wbooze has quit [Ping timeout: 252 seconds]
dionysus69 has joined #ruby
brw has quit [Remote host closed the connection]
brw has joined #ruby
wbooze has joined #ruby
<nakilon>
havenwood: remember I did the automatic reinitializing with Capybara?
<nakilon>
with it I could do smth like grid.with_retry{ ... } and that method would call the reinit() to reassign some @ storage inside
<nakilon>
I now wonder how to make the same for a slightly different class, i.e. while grid was a totally custom object with own API from scratch, I have a method that returns an array of them, such as `def tabs ; find_all(...).map{ |_| Tab.new _ }`; but the issue is that when some of Tab's methods faces the error I want to reinit the whole array
<nakilon>
I don't want to delegate the Array methods one by one in case of solving this via class Tabs
<nakilon>
but somehow I need to execute a block on a single tab object that would reinit the whole array of such objects
<nakilon>
should I use DelegateClass? its constructor glitches with irb/byebug
grenierm has quit [Quit: Client closed]
wbooze has quit [Quit: Leaving]
GreenResponse has joined #ruby
andy-turner has joined #ruby
user71 has joined #ruby
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #ruby
llua` has quit [Ping timeout: 248 seconds]
llua has joined #ruby
llua has quit [Ping timeout: 276 seconds]
llua has joined #ruby
llua has quit [Ping timeout: 276 seconds]
<nakilon>
made via manual definition of methods each, size, last
llua has joined #ruby
GreenResponse has quit [Ping timeout: 248 seconds]
llua has quit [Ping timeout: 252 seconds]
GreenResponse has joined #ruby
dionysus70 has joined #ruby
dionysus69 has quit [Read error: Connection reset by peer]
dionysus70 is now known as dionysus69
llua has joined #ruby
llua has quit [Ping timeout: 248 seconds]
llua has joined #ruby
llua has quit [Ping timeout: 245 seconds]
gr33n7007h has quit [Ping timeout: 248 seconds]
gr33n7007h has joined #ruby
R2robot has quit [Quit: Pull the lever, Kronk. Wrong leverrrrrrr!]
Linux_Kerio has joined #ruby
Linux_Kerio has quit [Read error: Connection reset by peer]
R2robot has joined #ruby
llua has joined #ruby
infinityfye has quit [Read error: Connection reset by peer]
infinityfye has joined #ruby
llua has quit [Ping timeout: 272 seconds]
mange has quit [Quit: Zzz...]
GreenResponse has quit [Quit: Leaving]
wbooze has joined #ruby
wbooze has quit [Remote host closed the connection]
wbooze has joined #ruby
trillion_exabyte has quit [Ping timeout: 244 seconds]
trillion_exabyte has joined #ruby
wbooze has quit [Quit: Leaving]
infinityfye has quit [Read error: Connection reset by peer]
llua has joined #ruby
llua has quit [Ping timeout: 252 seconds]
llua has joined #ruby
infinityfye has joined #ruby
wbooze has joined #ruby
Linux_Kerio has joined #ruby
wbooze has quit [Quit: Leaving]
llua has quit [Ping timeout: 252 seconds]
Guest64 has joined #ruby
Guest47 has joined #ruby
Guest47 has quit [Client Quit]
wbooze has joined #ruby
Guest64 has quit [Quit: Client closed]
elmetah has joined #ruby
elmetah has quit [Quit: Leaving]
llua has joined #ruby
llua has quit [Ping timeout: 260 seconds]
llua has joined #ruby
wbooze has quit [Quit: Leaving]
dionysus69 has quit [Ping timeout: 248 seconds]
oznek has joined #ruby
wbooze has joined #ruby
oznek has quit [Remote host closed the connection]
oznek has joined #ruby
GreenResponse has joined #ruby
llua has quit [Ping timeout: 252 seconds]
llua has joined #ruby
Sheilong has joined #ruby
jmcantrell has joined #ruby
kerzhak has joined #ruby
oznek_ has joined #ruby
oznek has quit [Ping timeout: 252 seconds]
brokkoli_originl has quit [Ping timeout: 252 seconds]
llua has quit [Ping timeout: 276 seconds]
brokkoli_originl has joined #ruby
schne1der has quit [Ping timeout: 268 seconds]
llua has joined #ruby
jmcantrell has quit [Ping timeout: 252 seconds]
infinityfye has quit [Read error: Connection reset by peer]
infinityfye has joined #ruby
Common-Lisp has joined #ruby
<Common-Lisp>
Is there any reason to choose Dir#mkdir over FileUtils#mkdir, or vice versa?
cappy has joined #ruby
schne1der has joined #ruby
Common-Lisp has quit [Ping timeout: 265 seconds]
user71 has quit [Quit: Leaving]
TomyWork has quit [Ping timeout: 248 seconds]
<havenwood>
Common-Lisp: The latter takes an Array if you want to make multiple directories at once and I like the kwarg style, but not really.
<havenwood>
I'd not usually bother with FileUtils dir-making unless it's for #mkdir_p. The #mkdir just seems tacked on for completeness and having parallel commonality with #mkdir_p.
<havenwood>
Dir.mkdir is fine!
zph1nx has quit [Quit: Bye!]
andy-turner has quit [Ping timeout: 252 seconds]
zphinx has joined #ruby
infinityfye has quit [Read error: Connection reset by peer]
<o0ox1eef>
I usually choose FileUtils because it is my default thanks to the other gadgets it has (like mkdir_p, etc). I'm not sure that can count as a reason though :D
<havenwood>
o0ox1eef: Yeah, when you've already done the `require 'file_utils'` it's less of a reach.
<o0ox1eef>
Agreed. And I think that is a good reason. 'Dir' is core Ruby while fileutils is stdlib.
jmcantrell has joined #ruby
Linux_Kerio has quit [Ping timeout: 268 seconds]
schne1der has quit [Ping timeout: 245 seconds]
jmcantrell has quit [Ping timeout: 252 seconds]
Milos has joined #ruby
wbooze has quit [Ping timeout: 252 seconds]
ruby[bot] has quit [Remote host closed the connection]
ruby[bot] has joined #ruby
GreenResponse has quit [Quit: Leaving]
cappy has quit [Quit: Leaving]
Munto has joined #ruby
Munto has quit [Remote host closed the connection]