Possible problem with Rust version

[brianoh]

I'm just starting now to learn Rust in order to compare it to Go and Dart primarily. I'm interested partly in testing database packages.

Attempting to compile rust-postgres resulted in the following error (win7):

c:\Users\Brian\rust-dev\dev\rust-postgres>rustc --lib lib.rs
lib.rs:922:8: 924:54 error: too many arguments to fmt!. found 3, expected 1
lib.rs:922 assert!(self.param_types.len() == params.len(),
lib.rs:923 "Expected {} parameters but found {}",
lib.rs:924 self.param_types.len(), params.len());

I presume that this is because I am not using the cutting-edge version.

Would it be feasible for you to freeze a release to keep it in step with the official release?

[sfackler]

Yeah, that's a version issue. assert! has switched from old-style fmt! formatting to the new format! system. Unfortunately, it's not actually possible to tag a commit that works on the 0.8 release, since there were some visibility issues that make it impossible to use extra::url::Url.

The official releases aren't really very official. They're simply snapshots taken every ~3 months, which sometimes results in unfortunate situations like this. If you're willing/able to compile Rust from source, I'd recommend that. There are nightly binary repositories for Ubuntu and Arch, but that won't help you if you're on Windows. There also plans in the works to make nightly binaries officially: rust-lang/rust#9877. I'll tag releases that work on releases 0.9 and out in the future when possible.