General

Profile

claytrump (Clay Trump)

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 1 1

Activity

06/07/2013

12:53 AM Ruby Feature #8499: Importing Hash#slice, Hash#slice!, Hash#except, and Hash#except! from ActiveSupport
Yay, +1 for `slice` & `except`
BTW, makes no sense to me if `h[:foo, :bar]` returns keys and values in a
hash while `h[:foo]` returns a value.
---
\<lay trum/\>
claytrump (Clay Trump)

11/17/2012

03:53 AM Ruby Feature #7322: Add a new operator name #>< for bit-wise "exclusive or"
Sorry, I didn't read the whole thread, but why not use the right operators?

g = 9.81 * m / s ** 2

--
<lay trum/>
claytrump (Clay Trump)

11/14/2012

02:53 PM Ruby Feature #7349: Struct#inspect needs more meaningful output
I like it too. Could even be:

Point.ancestors
# => [Point, Struct.new(:x, :y), Struct, Enumerable, Object, Kernel,
BasicObject]

--
<lay trum/>
claytrump (Clay Trump)

11/03/2012

01:53 PM Ruby Bug #6832: Module#instance_method and Module#method_defined? act inconsistently w.r.t #respond_to_missing?
+1, at least for instance_method returning an UnboundMethod.

On Fri, Nov 2, 2012 at 11:25 PM, mame (Yusuke Endoh) <mame@tsg.ne.jp> wrote:

>
> Issue #6832 has been updated by mame (Yusuke Endoh).
>
> Status changed from O...
claytrump (Clay Trump)

10/27/2012

05:23 AM Ruby Feature #1586: Including a module already present in ancestors should not be ignored
I'm looking forward to consistent module inclusion :-)

I should have talked about Marc-andre's example with multiple inclusion at
the same level (same class/module/object), coz I don't think it should be
done this way. The exam...
claytrump (Clay Trump)

08/13/2012

12:53 PM Ruby Feature #6847: Hash#extract
Oh my, what a disaster. I wonder who made the crazy decision that hash
slice would returned a slice of the hash and slice! would return... the
receiver and not the slice of the hash. Especially since Array slice and
slice! return ...
claytrump (Clay Trump)
01:23 AM Ruby Feature #6847: Hash#extract
> It's definitely like extract! in ActiveSupport, just non-destructive.


There is no "extract!" in ActiveSupport, its "slice!" you mean.

So yeah, I've used that before, and would be nice in core. I think it
should be calle...
claytrump (Clay Trump)

08/10/2012

02:53 AM Ruby Feature #6847: Hash#extract
Isn't that like the method slice in ActiveSupport?

On Thu, Aug 9, 2012 at 1:01 PM, citizen428 (Michael Kohl) <
citizen428@gmail.com> wrote:

>
> Issue #6847 has been reported by citizen428 (Michael Kohl).
>
> ----------...
claytrump (Clay Trump)

07/17/2012

07:53 AM Ruby Feature #6731: add new method "Object.present?" as a counter to #empty?
Hum, wouldn't this conflict with Rails? In Rails, " ".present? is
falseclass Object

>
> def present?
> !(respond_to?(:empty?) ? empty? : !self)
> end
>
> end
>
> --
<lay trum/>
claytrump (Clay Trump)

07/03/2012

12:23 AM Ruby Feature #4985: Add %S[] support for making a list of symbols
+1, I'd use that a lot.

Do we need two versions? Why not always interpolate? Can't see who's going
to need a symbol with a litteral #{ or \whatever in it.

This way we could have only %S and it always interpolates.
--
<l...
claytrump (Clay Trump)

Also available in: Atom