On Mon, Oct 21, 2013 at 4:33 PM, Dan Cristian Octavian <[email protected]> wrote: > Bumping this, because my deadline for choosing a master's project is 25th. > > Would appreciate it if somebody could give me a brief answer about my > concerns with regards to the runtimeless rust thing, at least. If I am > unclear please ask for clarifications. >
Hi Dan -- As a former grad student, the big piece of advice I have is to not make the success or lack thereof of your master's thesis topic depend on anything that's outside your control, which includes whether the Rust team decides to integrate your patch. It's nothing personal -- in open-source, code can fail to get integrated for a wide variety of reasons, not usually having to do with the submitter's lack of enthusiasm or skill -- just pragmatism. So I think you should choose a research question that you can formulate in a way that's independent of Rust. Then, make sure that whether or not your work succeeds or fails, you will have learned something. That way you can provide at least a partial answer to your research question even if your work ends up not being applicable to Rust. A good thesis topic is one that is guaranteed to contribute something to the literature whether it's in the form of a positive result or a negative result. I think you could potentially have a very strong thesis by formulating a question that's independent of any specific language, then explaining secondarily that as your case study, you will implement your approach as part of the Rust compiler. Then even if you don't have a finished solution at the end, you can write about your experiences. Cheers, Tim -- Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt "Being queer is not about a right to privacy; it is about the freedom to be public, to just be who we are." -- anonymous, June 1990 _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
