Re: [rust-dev] Rust and real-time audio

2014-10-08 Thread Allen Welkie
For your first question, you could enable the owned-heap-memory warning as an error for the crate in which you want to avoid heap memory. If this doesn't do exactly what you want, you may be able to write your own lint to do what you want http://doc.rust-lang.org/rustc/lint/ On Wed, Oct 8, 2014

Re: [rust-dev] Rust and real-time audio

2014-10-08 Thread David Henningsson
On 2014-10-08 13:02, Allen Welkie wrote: For your first question, you could enable the owned-heap-memory warning as an error for the crate in which you want to avoid heap memory. If this doesn't do exactly what you want, you may be able to write your own lint to do what you want

[rust-dev] Rust Research Project Query

2014-10-08 Thread Victor Barua
Dear Rust Developers, I'm a senior Computer Science undergraduate student at the University of British Columbia. As part of my degree I have to complete an undergraduate thesis which is a project of around 220 hours between now and next April. Rust is a language that has caught my eye and I would

[rust-dev] First impressions of Rust

2014-10-08 Thread Nathan Vegdahl
Hello Rust devs! I've been following Rust off-and-on for about a year, but in the last month I actually started trying to do some development in it. I haven't done a huge amount with Rust yet, but I'm hoping some first impressions from a newbie like myself might be useful. I come from a C++ and

Re: [rust-dev] First impressions of Rust

2014-10-08 Thread Alex Crichton
Disclaimer: please take all of this with a huge grain of salt. This feedback is meant with the humility of someone who surely doesn't fully understand the language yet and hasn't invested enough time into yet to be taken seriously. Much of what I say may have little bearing on anything.

Re: [rust-dev] First impressions of Rust

2014-10-08 Thread Lee Wei Yen
let mut v = vec!(1i, 2, 3, 4, 5); v[2] = 7; // Not allowed Instead I had to do: *v.get_mut(2) = 7; I have to admit, this caught me off guard as well. Was it a specific design decision? -- Lee Wei Yen On Thursday, October 9, 2014 at 7:36 AM, Nathan Vegdahl wrote: Hello Rust devs!

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Erick Tryzelaar
Hey there Victor, There are plenty of interesting projects that need to get done. The places I would suggest looking would be the active RFCs [1] and the interesting projects in our bug database [2]. Before you do anything though, you should check with the RFC author to see if someone's already

Re: [rust-dev] First impressions of Rust

2014-10-08 Thread Ben Foppa
Re: `mod`, `use`, and `extern crate`: My preferred solution so far has been to have one file that has the `extern crate` and `mod` statements (usually projectname.rs), and then my other files (e.g. main.rs) have only `use` statements. On Wed, Oct 8, 2014 at 1:36 PM, Nathan Vegdahl

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Sean McArthur
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

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Corey Richardson
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

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Manish Goregaokar
Servo has a bunch of student projects https://github.com/servo/servo/wiki/Student-projects that you might be interested in. -Manish Goregaokar On Thu, Oct 9, 2014 at 6:50 AM, Corey Richardson co...@octayn.net wrote: LLVM already has support for instrumenting code to generate gcov data, I

Re: [rust-dev] Rust crypto highlights

2014-10-08 Thread Palmer Cox
Regarding rust-crypto and timing attacks: in general the library tries to provide constant time implementations where possible. There are two implementations of AES - the AES-NI implementation and a bit-sliced pure software implementation. There isn't currently a table lookup based implementation

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Davis Silverman
Well, I've been looking forward to an actor library ( https://github.com/rust-lang/rust/issues/3573) although I think someone already wrote a paper on that. You could look into Rust's wishlist issues https://github.com/rust-lang/rust/labels/I-wishlist?page=3q=is%3Aopen+label%3AI-wishlist or the

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Tony Arcieri
On Wed, Oct 8, 2014 at 10:51 AM, Victor Barua victor.ba...@gmail.com wrote: I'm a senior Computer Science undergraduate student at the University of British Columbia. As part of my degree I have to complete an undergraduate thesis which is a project of around 220 hours between now and next

Re: [rust-dev] Rust Research Project Query

2014-10-08 Thread Alfie John
Hey Victor, On Wed, Oct 8, 2014, at 06:51 PM, Victor Barua wrote: I was hoping to ask the community for ideas on any tools, language features or research that would be useful to the community and fit the scope of 220 hours undergraduate project. I apologize in advance if this is the wrong

Re: [rust-dev] Rust crypto highlights

2014-10-08 Thread Tony Arcieri
On Wed, Oct 8, 2014 at 7:34 PM, Palmer Cox palmer...@gmail.com wrote: rust-crypto and timing attacks [...] AES-NI [...] no one has verified that LLVM optimizations [...] assembly code [...] build something like rust-constanttime Seems like an OK trajectory, but it would be good to verify if