Re: [rust-dev] Compiling with no bounds checking for vectors?

2014-03-28 Thread Matthew Frazier
I would just like to interject that this conversation has been blowing my
inbox up all morning and seems to be going absolutely nowhere. The people
on both sides of this issue have stated their arguments exhaustively, and I
neither believe that the Rust developers would ever introduce a flag that
disables such a wide-reaching safety features, nor that the advocates of
such a flag will understand why anytime this month.

I would therefore recommend that all participants cease sending messages to
this thread, so that other discussions can continue in peace.

Thanks,
Matthew Frazier
On Mar 28, 2014 9:35 AM, Tommi rusty.ga...@icloud.com wrote:

 On 28 Mar 2014, at 15:01, Huon Wilson dbau...@gmail.com wrote:

 [..] And anyway, as Daniel and Patrick say, if you don't need the utmost
 safety, then Rust isn't the language you're looking for: things like C++
 work well in the speed department, at the cost of safety


 Yes, it seems that Rust isn't the language for those people. But what I'm
 saying is that Rust *could* be the language for those people *too*, if it
 wanted to.

 Even those people who don't need the utmost safety might take it if it's
 deemed not too big of a hindrance on performance. But it's probably
 impossible to determine beforehand whether the performance hit caused by
 safety will be within acceptable limits or not. Which is why those people
 need to be able to make that decision after the (safe) code has been
 written and make the switch quickly to raw performance with a compiler flag.


 ___
 Rust-dev mailing list
 Rust-dev@mozilla.org
 https://mail.mozilla.org/listinfo/rust-dev


___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Deprecating rustpkg

2014-01-28 Thread Matthew Frazier

On 01/28/2014 04:33 AM, Lee Braiden wrote:

On 28/01/14 08:36, György Andrasek wrote:

I never quite understood the problem `rustpkg` was meant to solve. For
building Rust code, `rustc --out-dir build` is good enough. For
running tests and benchmarks, `rustc` is good enough. For downloading
things, I still need to feed it a github address, which kinda takes
away any value it could have over `git clone` or git submodules.

What I would actually need from a build system, i.e. finding
{C,C++,Rust} libraries, building {C,C++,Rust} libraries/executables
and linking them to said {C,C++,Rust} libraries, it doesn't do. It
also doesn't bootstrap rustc.


I agree with this.  What I'd want is much more like apt (add
repositories, update lists of available packages from those
repositories, manage priorities between repositories, say that one
repository should be preferred over another for a particular package,
working in specific prefixes (/usr/local, /usr, /,
~/Projects/something-requiring-old-libs), but rust-specific and platform
independent.


Have you ever used Composer https://getcomposer.org/? I know that 
Jordi Boggiano, one of the authors, has been involved with the Rust 
community in the past. Some Composer features that I think are critical 
for the new Rust package manager include:


- Tags and branches are automatically recognized from git to create 
versions.


- Version specifiers aren't just limited to this version exactly, but 
allow you to match on a range of versions (though Semantic Versioning is 
encouraged).


- Packages have vendor prefixes (like rust/flate or 
leafstorm/mycoollibrary) to help avoid name conflicts and allow for 
forking, but these aren't linked to the way packages are retrieved.


- There's a central repository, but it's really easy to add random git 
repositories to the composer.json, or to create your own repositories 
for internal use.


- It automatically generates a lock file that allows you to reinstall 
exactly the same versions of the dependencies across machines.


- Everything is installed per-project, so no conflicts across projects. 
(Though the new rustpkg may want to not do this exactly because of 
compile times.)


If I had more time and more Rust experience, I would be interested in 
implementing a Composer-like package manager for Rust. Unfortunately I 
have little of both. :-(

--
Thanks,
Matthew Frazier
http://leafstorm.us
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev