GitHub PushEvent at 2014-01-23 18:56:44
Repository: rust
Actor: korenchkin
Payload: {"shas":[["d2e31338779f177c596f08be863c71ea550bcb97","bed3f98d0a894717be46c58ffa90302af9946688@hlabs.org","Add @Spell clusters to Vim syntax file\n\nAdd @Spell clusters to Vim syntax highlighting file to do spell checking\nonly inside comments and strings","Dmitry Vasiliev",true],["188167c4b3ab42f1d0dc793365819afe28719df5","4e2bff145130fab50273c200e7ed134427db62ab@live.com","Introduced a chapter that describes how to perform callbacks from C to Rust","Matthias Einwag",true],["67d83ac40af2c2e20c44e4c16b53e500880a7439","4e2bff145130fab50273c200e7ed134427db62ab@live.com","Further details on channel idea","Matthias Einwag",true],["76967a008be228e96a48c92effabebcbab2ea881","07db86670a43ff858ed3efbfcca0b30c6a792f5e@gmail.com","Support linking of rlib files in rustpkg","Jan Niklas Hasse",true],["6ccc1e88b7bdfde84df408eb559197ba786dbb22","07db86670a43ff858ed3efbfcca0b30c6a792f5e@gmail.com","Fix indention","Jan Niklas Hasse",true],["393191d914a14aa1a0ad10ffe54ff23940671353","4e2bff145130fab50273c200e7ed134427db62ab@live.com","Update guide-ffi.md\n\nSimplified the first examples to demonstrate callbacks without other threads involved and shortened the elaboration about async callbacks.","Matthias Einwag",true],["065f936bf153f482e10779ebd45b077035a578e0","26021f1f4700496d68e21ef6d4a1b6945da4c8eb@pagerduty.com","doc: Boxes diagram shows enum value inside box.","Div Shekhar",true],["8f93d39c75ef7964ea1dfb5cd8155dd29e61b76b","26021f1f4700496d68e21ef6d4a1b6945da4c8eb@pagerduty.com","doc: add note below diagram about memory layout.","Div Shekhar",true],["32408a6e32ba396a8e5f4d183d6b80352dfad092","e0f4ba005148a59847558384ed637989fce7ce79@ic.ac.uk","Fixed bug when initialising bitv from bool=true","Alex Whitney",true],["4be3262058a151699cb66f95cbdcf39cf0263a83","19e794c1bad8f0914a9eb04e9876660727aa8f3b@gmail.com","syntax::ext: replace span_fatal with span_err in many places.\n\nThis means that compilation continues for longer, and so we can see more\nerrors per compile. This is mildly more user-friendly because it stops\nusers having to run rustc n times to see n macro errors: just run it\nonce to see all of them.","Huon Wilson",true],["0578c15abd5d889199f1e48db890a12ed4df3c67","41869d89223c8d9ab2a22b48686e3508c6cc0b54@wgz.org","Fixed typos in comments of librustc backend.","chromatic",true],["f52bd5e4b75c48d94876e3909c7bf6f8f0a1c26a","a6cc2cef7d25f27847876bdb81651755fcebacf0@mozilla.com","rustc: Feature gate `log_syntax!`. Closes #11602","Brian Anderson",true],["ae2a5ecbf600495a80ae4d99853a2ed2c8f6b5e9","28efa798da98745d6a98078b320edd33f229eda6@gmail.com","handle zero-size allocations correctly\n\nThe `malloc` family of functions may return a null pointer for a\nzero-size allocation, which should not be interpreted as an\nout-of-memory error.\n\nIf the implementation does not return a null pointer, then handling\nthis will result in memory savings for zero-size types.\n\nThis also switches some code to `malloc_raw` in order to maintain a\ncentralized point for handling out-of-memory in `rt::global_heap`.\n\nCloses #11634","Daniel Micay",true],["1e20960f794a820791d4cb64e35d7c03ec505065","f8800a61e50195b5e128e84204d223c2328d9074@gmail.com","Actually force a / in the path for ext crates\n\nIf the library is in the working directory, its path won't have a \"/\"\nwhich will cause dlopen to search /usr/lib etc. It turns out that Path\nauto-normalizes during joins so Path::new(\".\").join(path) is actually a\nno-op.","Steven Fackler",true],["b3c93b34f3fa81e9e2ade0cd05e0516faa7150ae","ffb4761cba839470133bee36aeb139f58d7dbaa9@sb.org","Make WindowsPath::new(\"C:foo\").root_path() return Some(\"C:\")","Kevin Ballard",true],["f13086f4571e13f712b9606fddbee47f40c40842","fa90a1997d4882d213aab2a4993e89213953b222@gmail.com","Expose platform independent path separators","Erick Tryzelaar",true],["99cde8482efaed4757422d24cd46de8fa64c92cb","bed3f98d0a894717be46c58ffa90302af9946688@hlabs.org","Ignore all newline characters in Base64 decoder\n\nIgnore all newline characters in Base64 decoder to make it compatible\nwith other Base64 decoders.","Dmitry Vasiliev",true],["4a78364d491ee2d3a49f4ed5e62f63cd5748d898","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Forbid unnecessary visibility on view items\n\nFor `use` statements, this means disallowing qualifiers when in functions and\ndisallowing `priv` outside of functions.\n\nFor `extern mod` statements, this means disallowing everything everywhere. It\nmay have been envisioned for `pub extern mod foo` to be a thing, but it\ncurrently doesn't do anything (resolve doesn't pick it up), so better to err on\nthe side of forwards-compatibility and forbid it entirely for now.\n\nCloses #9957","Alex Crichton",true],["27843133448df3315af1a07dc6700d7754709a97","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","rustc: Clean up error reporting\n\nThis commit re-works how the monitor() function works and how it both receives\nand transmits errors. There are a few cases in which the compiler can abort:\n\n1. A normal compiler error. In this case, the compiler raises a FatalError as\n   the failure value of the task. If this happens, then the monitor task does\n   nothing. It ignores all stderr output of the child task and it also\n   suppresses the failure message of the main task itself. This means that on a\n   normal compiler error just the error message itself is printed.\n\n2. A normal internal compiler error. These are invoked from sess.span_bug() and\n   friends. In these cases, they follow the same path (raising a FatalError),\n   but they will also print an ICE message which has a URL to go report a bug.\n\n3. An actual compiler bug. This happens whenever anything calls fail!() instead\n   of going through the session itself. In this case, we print out stuff about\n   RUST_LOG=2 and we by default capture all stderr and print via warn!() so it's\n   only printed out with the RUST_LOG var set.","Alex Crichton",true],["d37e2f79cc049331a6fbde3ae5cc75a8e08ecb08","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Disallow implementation of cross-crate priv traits\n\nTurns out we were just forgetting to encode the privacy for trais, and\neverything without privacy defaults to public!\n\nCloses #11593","Alex Crichton",true]],"size":132,"ref":"refs/heads/master","head":"657e3530225410d167d7f1ee827f15bc69cd965e"}