Thanks for the answer!

As I said, I really don't mean that list comprehensions should be added now
- just that they may be added some time later, and that they're likely to
use the same 'for' syntax.

I believe you're going to find that rust's audience will be much wider than
current C/C++ programmers. Say I want to write an application that is not
very computationally heavy. Which language should I choose? Java and C#
require a big runtime so hard to distribute, C# is windows-only, Java
startup time is annoying. Python is slow and too dynamic (hard time
refactoring). C/C++ will mean that I'll have to deal with segmentation
faults all the time. Rust will be a perfect choice.

See for example
http://roscidus.com/blog/blog/2013/06/09/choosing-a-python-replacement-for-0install/
-
0install is a package manager that is currently written in Python. The
developer is thinking of rewriting it in a different language. C/C++ are
not considered (and rightly so), but rust is, and currently it wins the
most points in the author's several comparisons! When rust will mature, it
will get a lot more points (startup time, dependencies, tracebacks,
standard library) and be a very clear winner.

So definitely, make the language as simple as you can for the 1.0 release -
it should be made as simple as possible, but not simpler. But I have the
feeling that I, as a mainly-python programmer (a bit of C too), am going to
enjoy rust quite a lot. And I actually think that with a bit of sugar and
some good libraries, I may enjoy rust programming more than I enjoy python
programming.

tl;dr Rust is already gaining a lot of interest from non C/C++ programmers.
I think they should be somewhere at the back of your mind when you are
designing rust.

Cheers.
Noam


On 13 June 2013 20:25, Tim Chevalier <[email protected]> wrote:

> At this point we're focusing on removing features from Rust. We're
> vanishingly unlikely to add list comprehensions at this point. Rust's
> audience is C and C++ programmers, who won't necessarily notice their
> absence anyway. (Personally, I almost never used list comprehensions
> when I programmed in Haskell -- I found using higher-order functions
> directly to be much more natural -- but that part is just my opinion.)
>
> Cheers,
> Tim
>
> --
> Tim Chevalier * http://catamorphism.org/ * Often in error, never in doubt
> "Not a riot, it's a rebellion." -- Boots Riley
> "Attention Bros and Trolls: When I call out your spew, I'm not angry,
> I'm defiant." -- Reg Braithwaite
>
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to