I'm interested, though rather busy right now (free after the second week of November)
-Manish Goregaokar On Mon, Nov 3, 2014 at 1:56 AM, Nick Cameron <[email protected]> wrote: > There currently isn't, but I'd like to add API for this as part of the > rustc::middle::save module. If anyone is interested in implementing that, > it shouldn't be too hard and I'd be happy to help out. > > Cheers, Nick > > On Sun, Nov 2, 2014 at 11:32 AM, Andreas Tolfsen <[email protected]> wrote: > >> On Sat, Nov 1, 2014 at 3:08 PM, Vladimir Pouzanov <[email protected]> >> wrote: >> > Is there any way to access compiler warnings and errors other than >> parsing >> > stdout? I'd prefer a bit more structured approach. >> >> Most editors such will understand the output format from the compiler: >> >> /home/ato/Code/wires/src/response.rs:30:17: 30:20 warning: unused >> variable: `msg`, #[warn(unused_variables)] on by default >> >> In Emacs there are a number of built-in functions to deal with the >> output in the compilation mode buffer: >> >> https://www.gnu.org/software/emacs/manual/html_node/emacs/Compilation-Mode.html >> >> In vi you can type :cwindow to access the compile window. >> >> And in Acme you can simply right-click somefile.rs:42:12 to go to >> column 12 in line 42 in somefile.rs. >> >> So the output the compiler gives is machine readable, and there are >> many more tools that understand it. >> _______________________________________________ >> Rust-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/rust-dev >> > > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
