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

Age	Commit message (Collapse)	Author	Lines
2020-07-27	mv std libs to library/	mark	-46/+0

2019-11-29	Format libstd with rustfmt	David Tolnay	-14/+14
	This commit applies rustfmt with rust-lang/rust's default settings to files in src/libstd that are not involved in any currently open PR to minimize merge conflicts. THe list of files involved in open PRs was determined by querying GitHub's GraphQL API with this script: https://gist.github.com/dtolnay/aa9c34993dc051a4f344d1b10e4487e8 With the list of files from the script in outstanding_files, the relevant commands were: $ find src/libstd -name '*.rs' \ \| xargs rustfmt --edition=2018 --unstable-features --skip-children $ rg libstd outstanding_files \| xargs git checkout -- Repeating this process several months apart should get us coverage of most of the rest of libstd. To confirm no funny business: $ git checkout $THIS_COMMIT^ $ git show --pretty= --name-only $THIS_COMMIT \ \| xargs rustfmt --edition=2018 --unstable-features --skip-children $ git diff $THIS_COMMIT # there should be no difference
2019-02-28	libstd => 2018	Taiki Endo	-3/+3

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-03-18	rustc_driver: get rid of extra thread on Unix	Tatsuyuki Ishi	-0/+4

2018-01-31	Use a range to identify SIGSEGV in stack guards	Josh Stone	-4/+5
	Previously, the `guard::init()` and `guard::current()` functions were returning a `usize` address representing the top of the stack guard, respectively for the main thread and for spawned threads. The `SIGSEGV` handler on `unix` targets checked if a fault was within one page below that address, if so reporting it as a stack overflow. Now `unix` targets report a `Range<usize>` representing the guard memory, so it can cover arbitrary guard sizes. Non-`unix` targets which always return `None` for guards now do so with `Option<!>`, so they don't pay any overhead. For `linux-gnu` in particular, the previous guard upper-bound was `stackaddr + guardsize`, as the protected memory was inside the stack. This was a glibc bug, and starting from 2.27 they are moving the guard past the end of the stack. However, there's no simple way for us to know where the guard page actually lies, so now we declare it as the whole range of `stackaddr ± guardsize`, and any fault therein will be called a stack overflow. This fixes #47863.
2017-08-15	use field init shorthand EVERYWHERE	Zack M. Davis	-2/+2
	Like #43008 (f668999), but _much more aggressive_.
2017-07-10	Use LocalKey::try_with in std	Lee Bousfield	-8/+3

2017-03-13	std: remove a workaround for privacy limitations that isn't necessary anymore	Sean Gillespie	-6/+1

2016-11-01	std: Move sys_common to libstd/sys_common	Brian Anderson	-0/+61
	Make the directory structure reflect the module structure. I've always found the existing structure confusing.