There has been some work done on generating gcov data based on: https://github.com/rust-lang/rust/issues/690
Looking at cover though there appear to be benefits of doing this at the language level. More importantly, at least for me, based on feedback from my supervisor implementing something like cover has multiple qualities that would make it a good thesis project (plus it looks like it would be fun) so that closes the deal for me. Thanks for the ideas everyone. On 8 October 2014 18:20, Corey Richardson <co...@octayn.net> wrote: > LLVM already has support for instrumenting code to generate gcov data, > I believe Luqman and Huon have looked into this, at least slightly. > > On Wed, Oct 8, 2014 at 9:09 PM, Sean McArthur <smcart...@mozilla.com> > wrote: > > A project I'd love to see (either separate, or eventually baked into the > > test harness), is test coverage data. Something like how Go's cover[1] > > works, by adding counters to the source code, seems simplest. I've > thought > > about this, and it could either be a CLI tool, like `rustc --cover > --test`, > > or a plugin. Perhaps including a `#![cover]` attribute in the crate or > > something. With a plugin, the Plugin Registrar would need to add the > ability > > to register a Visitor that can modify the AST. > > > > [1] http://blog.golang.org/cover > > > > _______________________________________________ > > Rust-dev mailing list > > Rust-dev@mozilla.org > > https://mail.mozilla.org/listinfo/rust-dev > > > > > > -- > http://octayn.net/ >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
