ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: normalperson@yhbt.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69739] [Ruby trunk - Feature #11307] [Open] exception-free non-blocking Queue#pop
Date: Thu, 25 Jun 2015 23:06:23 +0000	[thread overview]
Message-ID: <redmine.issue-11307.20150625230621.c6faf92648af66f4@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11307.20150625230621@ruby-lang.org

Issue #11307 has been reported by Eric Wong.

----------------------------------------
Feature #11307: exception-free non-blocking Queue#pop
https://bugs.ruby-lang.org/issues/11307

* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: Yukihiro Matsumoto
----------------------------------------
As we learned from the nonblocking IO APIs, exceptions are noisy with debugging
enabled and waste allocations on backtraces.  We should have a better way to do
non-blocking Queue#pop without raising exceptions, but I don't know what the API
should be...




-- 
https://bugs.ruby-lang.org/

           reply	other threads:[~2015-06-25 22:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <redmine.issue-11307.20150625230621@ruby-lang.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-11307.20150625230621.c6faf92648af66f4@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).