Eregon (Benoit Daloze) wrote in #note-69: > That's pretty slow and inefficient as it creates a new Struct subclass for every Hash it's applied to. > ... Um ok so I'm voting against a new syntax. It's not necessary. A simple method like...danh337 (Dan H)
Adding this here because a new method, something like `as_struct`, feels more Rubyish to me than a new syntax. I've been using this because it lets me define with standard Hash syntactic sugar, then access the object members with meth...danh337 (Dan H)
These `and` & `or` operators are good things. They are much more readable for one-liners in some cases. @matz @nobu I know you are super busy, but is there any way to move this forward?danh337 (Dan H)
byroot (Jean Boussier) wrote in #note-2: > Alright I've figured it out. [...] > ... WOW. @byroot you are champion. I knew I needed to "cast" the received data from a plain IO to a UNIXSocket, but I didn't read the `recv_io` docs, whic...danh337 (Dan H)
I have code that uses UNIXSocket.pair and fork to send data between parent and child. It seems to work fine for a small number of messages passed, but then fails with Errno::EBADF on the child pid writing to its socket received from t...danh337 (Dan H)
rubyFeedback (robert heiler) wrote in #note-18: > > And it feels like I cannot convince anyone here with any amount of rationale > ... This is a great response, cheers and thanks for your time. Honestly I never thought this was a huge ...danh337 (Dan H)
This is my last attempt to show why this named method is needed. The `driver.rb` file shows the patterns that apply to all sorts of code.danh337 (Dan H)
At one time there were other folks who cared about this, in #16295, but it feels like I'm the only one now. And it feels like I cannot convince anyone here with any amount of rationale. And it feels like more code examples won't be enoug...danh337 (Dan H)