From: ryand-ruby@zenspider.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:77496] [Ruby trunk Bug#12812] Added Coverage#result=
Date: Thu, 06 Oct 2016 03:30:45 +0000 [thread overview]
Message-ID: <redmine.journal-60762.20161006033044.76e90e388e323a25@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-12812.20161006002448@ruby-lang.org
Issue #12812 has been updated by Ryan Davis.
This patch url will stay up to date better than a file attachment. I'm getting feedback from Nobu and fixing things:
https://github.com/ruby/ruby/pull/1456.patch
----------------------------------------
Bug #12812: Added Coverage#result=
https://bugs.ruby-lang.org/issues/12812#change-60762
* Author: Ryan Davis
* Status: Assigned
* Priority: Normal
* Assignee: Yusuke Endoh
* ruby -v:
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Originally submitted here: https://github.com/ruby/ruby/pull/1456
This exposes Coverage.result in a slightly more writeable way and allows coverage analysis to reset to a baseline in a safe way.
Note, I wasn't able to figure out how to invalidate the cached pointers in the VM bytecode, so this does `rb_ary_replace` across all the arrays instead. I'd love to see this improved so it were cleaner.
This is ongoing work to improve the current state of code coverage analysis. I'll be giving a talk on this at rubyconf 2016.
I should also add, this applies cleanly to (at least) 2.3 as well.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2016-10-06 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-12812.20161006002448@ruby-lang.org>
2016-10-06 0:24 ` [ruby-core:77493] [Ruby trunk Bug#12812] Added Coverage#result= ryand-ruby
2016-10-06 0:32 ` [ruby-core:77494] [Ruby trunk Bug#12812][Assigned] " hsbt
2016-10-06 3:30 ` ryand-ruby [this message]
2019-01-21 8:37 ` [ruby-core:91206] [Ruby trunk Bug#12812] " mame
2019-04-27 22:27 ` [ruby-core:92450] " mame
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.journal-60762.20161006033044.76e90e388e323a25@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).