Add lockfiles ?

[maxsnew]

According to http://crates.io/faq.html#why-do-binaries-have-cargo.lock-in-version-control,-but-not-libraries? the convention is to checkin lockfiles for executables.

If we check in lockfiles for each of these examples then the only thing we have to worry about breaking builds is breaking changes from the nightlies. On the other hand fixing versions for Piston dependencies will likely lead to examples getting out of date.

I'm leaning towards adding them.

[bvssvni]

The purpose with the examples is to show how to do stuff with the latest version and to introduce new users to Piston.

[bvssvni]

We could add lockfiles and remove them later if there is any problem.

[TyOverby]

I suggest not keeping lockfiles tracked. This will force us to keep the examples building under the current Master revision.

[indiv0]

I am also against tracking lockfiles. While I agree with the convention for most cases, piston-examples is specifically meant to display examples of how to use the latest version of piston.

If we introduce lockfiles, that forces users to either match the included lockfiles (to be able to compile code derived from the examples) or figure out how to use piston from scratch.

[bvssvni]

Ok, then we choose to not track them for now. Rationale #75

Closing this discussion.