Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread James Gao
7d818abf16c0061278658b8cfc6e0e0859885b5f *rust-0.5.tar.gz downloaded stage0 binary: *rust-0.5\dl\rust-stage0\bin\rustc.exe* is still failed to execute on *Win8 x64*. Error message is The application was unable to start correctly (0xc142). Click OK to close the application. The crash binary

Re: [rust-dev] purely function red-black tree

2012-12-20 Thread Niko Matsakis
Hello, While Patrick's advice to avoid @ is good in general, in this case I think it does not apply. Persistent or purely functional data structures basically must use @ so that they can share pointers into their internal nodes. I do hope that when Rust's libraries become more mature we

Re: [rust-dev] Warn about implicit integer conversion

2012-12-20 Thread Graydon Hoare
On 12-12-20 11:17 AM, Niko Matsakis wrote: This makes sense. What I really meant was: Let's not try to do this checking during the type check itself, as we initially did, but rather as a later lint step. This also allows you to disable it if you know what you're doing and for some reason the

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread Graydon Hoare
On 12-12-20 03:34 AM, James Gao wrote: 7d818abf16c0061278658b8cfc6e0e0859885b5f *rust-0.5.tar.gz downloaded stage0 binary: *rust-0.5\dl\rust-stage0\bin\rustc.exe* is still failed to execute on *Win8 x64*. Error message is The application was unable to start correctly (0xc142). Click OK

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread John Mija
I've Windows XP under VirtualBox. I'll test it tomorrow. El 20/12/12 20:05, Graydon Hoare escribió: On 12-12-20 03:34 AM, James Gao wrote: 7d818abf16c0061278658b8cfc6e0e0859885b5f *rust-0.5.tar.gz downloaded stage0 binary: *rust-0.5\dl\rust-stage0\bin\rustc.exe* is still failed to execute on

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread Brian Anderson
- Original Message - From: Graydon Hoare gray...@mozilla.com To: rust-dev@mozilla.org Sent: Thursday, December 20, 2012 2:53:58 PM Subject: Re: [rust-dev] 0.5 prerelease testing On 12-12-20 01:03 PM, Brian Anderson wrote: I'll test on Windows 7 x64 today. What's the status of

Re: [rust-dev] net::tcp::TcpSocket slow?

2012-12-20 Thread Brian Anderson
On 12/20/2012 05:58 PM, Michael Neumann wrote: Hi, I am writing a redis client [1] for rust but somehow TCP performance seems to be veery slow. I basically just sent a string to redis and read the response (I commented out parsing). Doing this 10_000 times takes about 4.5 seconds, while doing

Re: [rust-dev] Use of moved variable

2012-12-20 Thread Eric Holk
You could use vec::from_slice [1] to convert a slice to a unique vector, although for really performance sensitive work this may not be desirable because it introduces an extra copy. The better option is probably to see if it's possible to rewrite TcpSocket.write to use [u8] instead. I'd be

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread James Gao
The same problem occurs, Win8 Ent RTM 64bit, chcp=936. I found that rustrt.dll depends on some MingW dll, which version of MingW should I use? On Fri, Dec 21, 2012 at 6:53 AM, Graydon Hoare gray...@mozilla.com wrote: Candidate builds are up:

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread James Gao
rustc.exe from installer is also crash, here I dump some information from WinDbg: 0:000 g (1d50.c1c): Access violation - code c005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=43467590 ebx=

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread Graydon Hoare
On 12-12-20 07:42 PM, James Gao wrote: Confirm the problem here is caused by incompatible version of libstdc++-6.dll, I copy an old version libstdc++-6.dll, then rustc works fine. Can we pack the correct libstdc++-6.dll in the installer and stage0 snapshot packages? I'm afraid not, not

Re: [rust-dev] 0.5 prerelease testing

2012-12-20 Thread Graydon Hoare
On 12-12-20 08:33 PM, James Gao wrote: OK, how about supply a seperate package for these this run-time dll, or give the exact version/hash for the dll? We point directly to the version of mingw we test with on the website.