On Sat, Jun 1, 2013 at 3:45 AM, Graydon Hoare <[email protected]> wrote:
> I'll take that as a vote for a lint flag. Maybe set to warning level by > default? > > (Our lints can be set from anything between allow and forbid, the latter > meaning not just "error" but also "nobody else can override this in this > crate, I don't care what they think") > lint flag is better than nothing. However, like coding style, I prefer that machine-checkable code constraints should be strictly and uniformly enforced. Being able to explicitly set severity in the crate is better than what we have for C/C++, but over time it could still inhibit people moving code between crates. Rob -- q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
