rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2012-10-04	Forbid deprecated modes again in core	Tim Chevalier	-1/+1
	Sadly, there's only one file that requires deprecated modes (stackwalk)... So, forbid them everywhere else.
2012-10-02	Removing explicit uses of + mode	Tim Chevalier	-4/+3
	This removes most explicit uses of the + argument mode. Pending a snapshot, I had to remove the forbid(deprecated_modes) pragma from a bunch of files. I'll put it back! + mode still has to be used in a few places for functions that get moved (see task.rs) The changes outside core and std are due to the to_bytes trait and making the compiler (with legacy modes on) agree with the libraries (with legacy modes off) about modes.
2012-09-28	core: Demode patterns	Brian Anderson	-2/+2

2012-09-26	libcore: De-export cleanup, cmath, future, gc, hash, iter-trait, mutable, ↵	Patrick Walton	-12/+11
	and private
2012-09-18	core: Rename 'unsafe' mod to 'cast'	Brian Anderson	-1/+1

2012-09-10	Make all moves explicit in libsyntax	Tim Chevalier	-1/+1

2012-09-10	Rename the poorly named Managed<T> type to Mut<T>.	Niko Matsakis	-0/+151
	The Mut<T> type is intended to allow freezable data stuctures to be stored in `@mut` boxes. Currently this causes borrowck to be very conserivative since it cannot prove that you are not modifying such a structure while iterating over it, for example. But if you do `@Mut<T>` instead of `@mut T`, you will effectively convert borrowck's static checks into dynamic ones. This lets you use the e.g. send_map just like a Java Map or something else.