Re: [rust-dev] Questions about rust's OO.

2012-08-29 Thread Brian Anderson
On 08/29/2012 11:35 AM, Emmanuel Surleau wrote: [snip] Given a lot of assumptions about what might ultimately be available in the language, this looks like the beginnings of a workable design. Unfortunately, given the stateful nature of a test suite, you aren't going to be able to run the

Re: [rust-dev] Questions about rust's OO.

2012-08-27 Thread Niko Matsakis
Aside from the reflective aspects of JUnit, I think that the closest analogue in Rust to the use of inheritance to provide overridable methods like setup() and teardown() would be default methods in traits. Something like: trait TestSuite { fn setup() {} fn teardown() {} } struct

Re: [rust-dev] Questions about rust's OO.

2012-08-27 Thread Brian Anderson
On 08/26/2012 06:33 PM, Steve Jenson wrote: Hi rustics, I spent some time this weekend going over the rust tutorial and documentation for 0.3.1. I thought a fun exercise would be writing an xUnit testing framework[1] in a classic OO style. I ran into a few problems: I'm glad you've been

Re: [rust-dev] Questions about rust's OO.

2012-08-26 Thread Tim Chevalier
On Sun, Aug 26, 2012 at 6:33 PM, Steve Jenson ste...@fruitless.org wrote: Hi rustics, I spent some time this weekend going over the rust tutorial and documentation for 0.3.1. I thought a fun exercise would be writing an xUnit testing framework[1] in a classic OO style. I ran into a few

Re: [rust-dev] Questions about rust's OO.

2012-08-26 Thread Steve Jenson
On Sun, Aug 26, 2012 at 6:45 PM, Tim Chevalier catamorph...@gmail.com wrote: On Sun, Aug 26, 2012 at 6:33 PM, Steve Jenson ste...@fruitless.org wrote: Hi rustics, I spent some time this weekend going over the rust tutorial and documentation for 0.3.1. I thought a fun exercise would be writing