Dependency Compile Issue in Stable Rust Branch

[ChurroLoco]

I'm new to rust and this project looked really interesting so I tried to build it and got this error message with my stable version of rustc. I'm not sure if there is an easy fix for this in the Playform repo or a given requirement is to have the nightly rust build for now...

Also, I'm interesting in contributing if I can. Is there a mailing list for this project?

Rust Version

rustc 1.4.0 (8ab8581f6 2015-10-27)

Compile Errors

/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:1:1: 1:42 error: #[feature] may not be used on the stable release channel
/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:1 #![feature(plugin_registrar, box_syntax)]
                                                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:2:1: 2:46 error: #[feature] may not be used on the stable release channel
/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:2 #![feature(rustc_private, core, collections)]
                                                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:3:1: 3:28 error: #[feature] may not be used on the stable release channel
/.../.cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.21/src/lib.rs:3 #![feature(num_bits_bytes)]

[bfops]

Hey there!

Playform should build with whatever version is listed in the README, but it's not unlikely for it to be broken with newer nightlies or on the stable branch. Clippy is especially finicky. I install with ./rustup.sh --channel=nightly --date=2015-10-28. I haven't tried updating rustc past that.

It's also probably worth saying that Playform is possibly abandoned from my point of view. I'm taking a break and looking into Unity and Cubiquity, in part because I'm tired of reinventing all the wheels :). That said, I'm still happy to help anybody who's interested in maintaining/using/rewriting Playform. A lot of the code has been shifted in the client-voxels branch (specifically, a lot of the "chunk" code was taken out, and the client does it's own voxel-to-mesh conversion, instead of the server), so most changes should ideally happen there, but the performance is a lot worse there.

There's no mailing list. I'm subscribed to email updates, but so far everything's taken place via Github. It's been almost entirely me so far, so that hasn't really been a pain point.

[ChurroLoco]

Thanks for the update! After looking through the code a bit, I think it might be a little over my head right now. The more I read into the Rust the more I realized how different it was and I might need to start with some simpler projects. However I think might revisit this in a couple weeks.

It's funning you mentioning moving to Unity. My day-to-day job has me in a Unity all time for the past few years, and I have recently been feeling the itch to exercise my ability to do more low level stuff once again.

[bfops]

The code here is also nowhere near nice. Lots of tech debt :). I'm sure I'll find my own pain points with unity, but rust is so immature that just about everything has to be done from scratch, and it can't link to more developed C++ libraries, which would be the other option. Happy hacking!