General

Profile

wardrop (Tom Wardrop)

  • Login: wardrop
  • Email: tom@tomwardrop.com
  • Registered on: 12/23/2010
  • Last sign in: 11/11/2021

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 8 6 14

Activity

10/30/2017

03:56 AM Ruby Feature #10183: An alternative name for method `class`
Came here to make a similar feature suggestion. Ideally `class` would be aliased as something such as `klass` which has become somewhat of a ruby idiom to avoid collision with the `class` keyword. Though I'd also be interested to discuss... wardrop (Tom Wardrop)

08/13/2017

10:52 PM Ruby Feature #13805: Make refinement scoping to be like that of constants
jeremyevans0 (Jeremy Evans) wrote:
> You probably want to read the very long issue that introduced refinements (#4085), which contains the reasoning.
I thought there'd be one of these long discussions floating around, thanks for the ...
wardrop (Tom Wardrop)

08/11/2017

04:58 AM Ruby Feature #13805 (Open): Make refinement scoping to be like that of constants
Refinements are currently lexically scoped, which makes their use burdensome when one wants to apply a refinement to an entire project, requiring boiler plate at the top of every project file. I propose that there ought to be a method of... wardrop (Tom Wardrop)

10/18/2016

03:55 AM Ruby Feature #9108: Hash sub-selections
Indeed, I'm still hanging out for this. Seems like such a common thing I run into, and I'm always surprised this functionality isn't built in. `Hash#select { |k,v| {...}.include?(k) }` is very verbose. wardrop (Tom Wardrop)

01/22/2014

01:58 AM Ruby Feature #9428: Inline argument expressions and re-assignment
Indeed limiting it to method calls on the argument object (e.g `arg.to_i`) would make it much easier to parse and more readable, but greatly limits the potential application. It seems the inferencing in the initial proposal is the cause ... wardrop (Tom Wardrop)

01/21/2014

03:03 AM Ruby Feature #9428: Inline argument expressions and re-assignment
> I do not see why the person or machine that reads the first line of method's definition needs to know how the arguments will be post-processed before being further post-processed
Semantically, it just seems more appropriate to defin...
wardrop (Tom Wardrop)

01/20/2014

02:59 AM Ruby Feature #9428: Inline argument expressions and re-assignment
> "First encountered" in regular left-to-right parsing order?
It would be first identifier encountered as per the order of execution. In the following example, the variable in the if statement would be the name of the argument.
...
wardrop (Tom Wardrop)
12:41 AM Ruby Feature #9428: Inline argument expressions and re-assignment
1. I know you said you're not a fan of allowing expression when assigning default values to optional parameters, but the point about aesthetics applies equally to them also.
1. The rule is relatively simple. The first identifier (lvar...
wardrop (Tom Wardrop)

01/19/2014

11:28 PM Ruby Feature #9428: Inline argument expressions and re-assignment
Without syntax highlighting, it isn't super obvious, but in simple cases (which are the main use case), like `fetch(id.to_i)`, it is obvious enough without the aid of syntax highlighting.
Remember though, while there are aspects to t...
wardrop (Tom Wardrop)
12:39 PM Ruby Feature #9428: Inline argument expressions and re-assignment
Haha. I don't think any programming language exists that does anything even similar to this. Whether it's a good idea or not, it's going to provoke all the feelings that come with unfamiliarity. Everything is confusing until you learn it... wardrop (Tom Wardrop)

Also available in: Atom