<nakilon>
positional arguments are cognitive overhead
<nakilon>
yeah I didn't understand at start what's the purpose of cycle there
<nakilon>
I've got a question
<nakilon>
I have a method that does some calculations and then calls MyClass.new with the results to build an object with some handy methods
<nakilon>
sometimes the object "corrupts", i.e. its methods start throwing different exceptions and that means I have to reinstantiate my class
<nakilon>
this object is used all over the places, it many files, and so I don't want to put begin-rescue in so many places -- instead I want the MyClass to catch the exception and reinit itself
<nakilon>
but to call MyClass.new from within the methods of itself feels wrong
<nakilon>
I need to somehow repeat that "calculations" routine I do to pass the results to the ::new
<nakilon>
also I didn't want to move the calculations to constructor; I wanted to the "initialize" to accept already calculated data to just store them as attributes and do no more processing at that moment
___nick___ has joined #ruby
___nick___ has quit [Client Quit]
<havenwood>
nakilon: For your particular case, it sounds like you might consider a `rescue` inside your #initialize with a `retry` rather than a separate init helper method.
<havenwood>
For the SO question, I'd have recommended using #clear rather than fresh Arrays to reduce object churn and for clarity.
<nakilon>
i.e. not to have the exceptions of "unable to calculate the results" from within the class; but maybe that's where I do a mistake; maybe if the event "reinit" exists then I should allow it happen from within the class and stop hesitating making initialize fat
<havenwood>
And yeah, you might wanna not retry infinitely. :)
<nakilon>
the subject is a wrapper on Capybara, so I init a thing that represents, for example, a Table with useful methods, and if there was animation or slow loafing the found nodes might be corrupted, dead, not rectangular, etc., so I need to reinit my structure
<nakilon>
*loading
<nakilon>
*not transposable
<nakilon>
for example, JS can be made in the way that it recreated the <td> and after some scroll or click the node is gone
<nakilon>
and I need to handle this for guys who use the library
<nakilon>
havenwood: your gist; how often did you do things like this? is this a real practice?
<nakilon>
I just never did a thing a that would reinit itself
<nakilon>
for example, pretty sure it's impossible in basic class, like in Array you can't call self.replace from within a custom method
Linux_Kerio has joined #ruby
Linux_Kerio has quit [Read error: Connection reset by peer]
<nakilon>
for custom classes it's possible to assign the attributes at any time, but is it ruby-idiomatic
___nick___ has quit [Ping timeout: 252 seconds]
___nick___ has joined #ruby
STASIdownunder has joined #ruby
<nakilon>
maybe I can do it via assigning nils to memoized attributes, so the resetting will happen not in initialize but elsewhere on demand
STASIdownunder has quit [Read error: Connection reset by peer]
<havenwood>
nakilon: Using retry with rescue in a method is for sure real practice. Agree it's not common to have initialization raising. Hopefully it's rather exceptional.
STASIdownunder has joined #ruby
<havenwood>
nakilon: It's best to assign instance variables during initialization, but it doesn't matter if you use a helper method or not. It's fine to reassign them later, but nice to do instance variable assignment and any freezing up front to establish a single object shape.
factor4 has joined #ruby
<havenwood>
As long as multiple instances of the class assign instance variables initially, up front in the same order, they'll be the same shape which can be really beneficial if you have lots of them. It's generally a good practice for code readability but object shapes give a good additional reason to set them during initialization rather than later, even
<havenwood>
if they're going to be set again. A `nil` is a fine placeholder.
factor has quit [Ping timeout: 248 seconds]
factor4 is now known as factor
grenierm has quit [Ping timeout: 240 seconds]
STASIdownunder has quit [Read error: Connection reset by peer]
<nakilon>
meanwhile, "up front to establish a single object shape." -- the thing that "let" in rspec is avoiding
<nakilon>
I pray every day for my coworkers not to ask me when to let and when to def