• thedeemon (3/3) Mar 12 2013 Documentation for this method says it takes a value from the
• jerro (4/7) Mar 12 2013 Judging by the name, I think documentation shouldn't even specify
• monarch_dodra (5/12) Mar 12 2013 The behavior of removeAny is implementation defined.
• Andrei Alexandrescu (3/6) Mar 12 2013 Fix documentation. Thanks!

"thedeemon" <dlang thedeemon.com> writes:

Documentation for this method says it takes a value from the 
front, but the code actually does the opposite, takes it from the 
back. Shall we fix documentation or the code?

"jerro" <a a.com> writes:

On Tuesday, 12 March 2013 at 12:31:45 UTC, thedeemon wrote:
 Documentation for this method says it takes a value from the 
 front, but the code actually does the opposite, takes it from 
 the back. Shall we fix documentation or the code?

Judging by the name, I think documentation shouldn't even specify 
which element is removed. There are removeFront and removeBack if 
you want to remove front or back.

"monarch_dodra" <monarchdodra gmail.com> writes:

On Tuesday, 12 March 2013 at 12:52:20 UTC, jerro wrote:
 On Tuesday, 12 March 2013 at 12:31:45 UTC, thedeemon wrote:
 Documentation for this method says it takes a value from the 
 front, but the code actually does the opposite, takes it from 
 the back. Shall we fix documentation or the code?

 Judging by the name, I think documentation shouldn't even 
 specify which element is removed. There are removeFront and 
 removeBack if you want to remove front or back.

The behavior of removeAny is implementation defined. 
Documentation should be fixed.

Note that removeAny, contrary to the other removes returns will 
give you the element that was removed.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 3/12/13 8:31 AM, thedeemon wrote:
 Documentation for this method says it takes a value from the front, but
 the code actually does the opposite, takes it from the back. Shall we
 fix documentation or the code?

Fix documentation. Thanks!

Andrei