[#5322] O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...>

I just did some benchmarks on push, pop, shift, and unshift

24 messages 2005/07/01
[#5338] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/02

On Fri, 1 Jul 2005, Eric Mahurin wrote:

[#5348] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/02

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5357] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sat, 2 Jul 2005, Eric Mahurin wrote:

[#5359] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5361] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sun, 3 Jul 2005, Eric Mahurin wrote:

[#5362] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5365] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5367] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/04

--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

[#5368] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5372] Re: O(1) performance for insertions/deletions at the front of an Array/String — Florian Gro<florgro@...> 2005/07/04

Yukihiro Matsumoto wrote:

[#5420] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...>

Sydney, an experimental ruby interpreter, has been released!

15 messages 2005/07/11
[#5424] Re: [ANN] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...> 2005/07/12

Thanks everyone for the feedback so far!

Re: Observer patch

From: nornagon <nornagon@...>
Date: 2005-07-30 12:35:59 UTC
List: ruby-core #5519
On 7/9/05, Hugh Sasse <hgs@dmu.ac.uk> wrote:
> On Fri, 8 Jul 2005, nornagon wrote:
> >
> > [snip]
> >
> >  # Add +observer+ as an observer on this object. +observer+ will now receive
> >  # notifications.
> 
> You've changed how this is called.  IMHO you should patch the
> leading RDOC comment.
> 
> >  [snip]
> > +    @observer_peers = {} unless defined? @observer_peers
> 
> is
> 
>         @observer_peers ||= {}
> 
> more idiomatic?   Performance??
> 
> > [snip]
> > +       @observer_peers.each { |k, v|
> > +      k.send v, *arg
> > +    }
> 
> if nitpick.allowed? -- aren't we moving towards having {} for
> one-liners and do...end for multi-line blocks?  Giving 2 possible
> patches for this patch :-)

I won't bother applying those changes unless this is going to go into
the core -- which I believe it should; it's a trivial patch that adds
a lot of flexibility to Observable.

If it is going to go into the core, I'll just add those changes and
repost the patch, unless someone does it before I do. :)

-- 
- nornagon


In This Thread

Prev Next