On Thu, Feb 14, 2013 at 10:49 PM, Brian Smith wrote:
> For example, Rust can't, in general, stop you from writing "if (!x)" instead
> of "if (x)" like I did in a recent NSS bug.
Depending on what 'x' is and how it was obtained it's possible it
could be stopped. If it's a null pointer check for e
On Sun, Feb 10, 2013 at 9:44 AM, L. David Baron wrote:
> For some languages (e.g., HTML, and possibly also CSS) parsing could
> be relatively parallizable by splitting up the input into chunks and
> parsing each chunk by speculating on a likely state at the start of
> the chunk, having slight over
2 matches
Mail list logo
