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

Age	Commit message (Collapse)	Author	Lines
2019-01-03	Fix repeated word typos	Wiktor Kuchta	-1/+1
	Found with `git grep -P '\b([a-z]+)\s+\1\b'`
2018-12-28	Auto merge of #55519 - fhartwig:hashmap-index-example, r=Centril	bors	-0/+3
	Add example of using the indexing operator to HashMap docs Fixes #52575
2018-12-25	Remove licenses	Mark Rousskov	-60/+0

2018-12-23	Rollup merge of #57050 - RyanMarcus:master, r=zackmdavis	kennytm	-1/+1
	Fixed typo in HashMap documentation Previously "with a custom type as key", now "with a custom key type"
2018-12-21	Fixed typo in HashMap documentation	Ryan Marcus	-1/+1
	Previously "with a custom type as key", now "with a custom key type"
2018-12-21	Inline tweaks	John Kåre Alsaker	-0/+3

2018-12-07	Various minor/cosmetic improvements to code	Alexander Regueiro	-6/+6

2018-12-07	Rollup merge of #56561 - Zoxc:too-raw, r=Gankro	kennytm	-0/+4
	Fix bug in from_key_hashed_nocheck
2018-12-06	Fix bug in from_key_hashed_nocheck	John Kåre Alsaker	-0/+4

2018-12-04	Replace usages of `..i + 1` ranges with `..=i`.	Corey Farwell	-2/+2

2018-12-02	Update issue number of `shrink_to` methods to point the tracking issue	Hidehito Yabuuchi	-2/+2

2018-11-30	Inline things	John Kåre Alsaker	-0/+11

2018-11-22	Fix the tracking issue for hash_raw_entry	Steven Fackler	-38/+38
	It used to point to the implementation PR.
2018-11-22	Rollup merge of #55784 - meltinglava:master, r=KodrAus	Guillaume Gomez	-8/+8
	Clarifying documentation for collections::hash_map::Entry::or_insert Previous version does not show that or_insert does not insert the passed value, as the passed value was the same value as what was already in the map.
2018-11-13	fix various typos in doc comments	Andy Russell	-1/+1

2018-11-13	The example values are now easyer to differenciate	Meltinglava	-8/+8

2018-11-08	Clarifying documentation for collections::hash_map::Entry::or_insert	Meltinglava	-2/+2
	Previous version does not show that or_insert does not insert the passed value, as the passed value was the same value as what was already in the map.
2018-11-07	Rollup merge of #55734 - teresy:shorthand-fields, r=davidtwco	kennytm	-1/+1
	refactor: use shorthand fields refactor: use shorthand for single fields everywhere (excluding tests).
2018-11-06	refactor: use shorthand fields	teresy	-1/+1

2018-11-02	Auto merge of #54043 - fintelia:raw_entry, r=alexcrichton	bors	-6/+672
	Add raw_entry API to HashMap This is a continuation of #50821.
2018-10-31	A couple suggested edits	Jonathan Behrens	-7/+3

2018-10-30	Add example of using the indexing operator to HashMap docs	Florian Hartwig	-0/+3

2018-09-16	Auto merge of #53804 - RalfJung:ptr-invalid, r=nagisa	bors	-1/+3
	fix some uses of pointer intrinsics with invalid pointers [Found by miri](https://github.com/solson/miri/pull/446): * `Vec::into_iter` calls `ptr::read` (and the underlying `copy_nonoverlapping`) with an unaligned pointer to a ZST. [According to LLVM devs](https://bugs.llvm.org/show_bug.cgi?id=38583), this is UB because it contradicts the metadata we are attaching to that pointer. * `HashMap` creation calls `ptr:.write_bytes` on a NULL pointer with a count of 0. This is likely not currently UB currently, but it violates the rules we are setting in https://github.com/rust-lang/rust/pull/53783, and we might want to exploit those rules later (e.g. with more `nonnull` attributes for LLVM). Probably what `HashMap` really should do is use `NonNull::dangling()` instead of 0 for the empty case, but that would require a more careful analysis of the code. It seems like ideally, we should do a review of usage of such intrinsics all over libstd to ensure that they use valid pointers even when the size is 0. Is it worth opening an issue for that?
2018-09-13	Entry is an enum not a struct	Jonathan Behrens	-1/+1

2018-09-13	Fix links in docs	Jonathan Behrens	-2/+7

2018-09-13	Eliminate unused variable warning	Jonathan Behrens	-1/+1

2018-09-13	Fix tests and update issue number	Jonathan Behrens	-138/+156

2018-09-13	Remove println!() statement from HashMap unit test	Jonathan Behrens	-1/+0

2018-09-12	Fix formatting	Jonathan Behrens	-1/+2

2018-09-10	fix typos in growth algo description	Val	-4/+4
	modified to read "the first table overflows into the second, and the second into the first." plus smaller typos
2018-09-07	Cleanup API somewhat	Jonathan Behrens	-217/+195

2018-09-06	Fix invalid urls	Guillaume Gomez	-3/+2

2018-09-05	disambiguate hashes	Alexis Beingessner	-3/+3

2018-09-05	fixup Debug bounds	Alexis Beingessner	-2/+2

2018-09-05	progress on raw_entry	Alexis Beingessner	-229/+231

2018-09-05	WIP: add raw_entry API to HashMap	Alexis Beingessner	-37/+703

2018-08-29	fix some uses of pointer intrinsics with invalid pointers	Ralf Jung	-1/+3

2018-08-20	Replace usages of ptr::offset with ptr::{add,sub}.	Corey Farwell	-2/+2

2018-06-29	Move core::alloc::CollectionAllocErr to alloc::collections	Simon Sapin	-3/+4

2018-06-29	Move some alloc crate top-level items to a new alloc::collections module	Simon Sapin	-4/+4
	This matches std::collections
2018-06-19	Auto merge of #51543 - SimonSapin:oom, r=SimonSapin	bors	-2/+2
	Rename OOM to allocation error The acronym is not descriptive unless one has seen it before. * Rename the `oom` function to `handle_alloc_error`. It was stabilized in 1.28, so if we do this at all we need to land it this cycle. * Rename `set_oom_hook` to `set_alloc_error_hook` * Rename `take_oom_hook` to `take_alloc_error_hook` Bikeshed: `on` v.s. `for`, `alloc` v.s. `allocator`, `error` v.s. `failure`
2018-06-18	Rename OOM to allocation error	Simon Sapin	-2/+2
	The acronym is not descriptive unless one has seen it before. * Rename the `oom` function to `handle_alloc_error`. It was stabilized in 1.28, so if we do this at all we need to land it this cycle. * Rename `set_oom_hook` to `set_alloc_error_hook` * Rename `take_oom_hook` to `take_alloc_error_hook` Bikeshed: `alloc` v.s. `allocator`, `error` v.s. `failure`
2018-06-18	Prefer use of owned values in examples	Kornel	-23/+37

2018-06-11	Remove deprecated heap modules	Simon Sapin	-1/+1
	The heap.rs file was already unused.
2018-06-11	Remove alloc::Opaque and use *mut u8 as pointer type for GlobalAlloc	Mike Hommey	-1/+1

2018-06-10	Stabilize entry-or-default	Guillaume Gomez	-3/+1

2018-06-04	Optimize layout calculations in HashMap	Amanieu d'Antras	-3/+16
	This now produces the same assembly code as the previous implementation.
2018-06-02	Add a couple lines describing differences between into_mut/get_mut.	Corey Farwell	-0/+9

2018-06-02	Fixed typo	Phlosioneer	-1/+1

2018-06-02	Clarify the difference between get_mut and into_mut for OccupiedEntry	Phlosioneer	-2/+6
	The examples for both hash_map::OccupiedEntry::get_mut and hash_map::OccupiedEntry::into_mut were almost identical. This led to some confusion over the difference, namely why you would ever use get_mut when into_mut gives alonger lifetime. Reddit thread: https://www.reddit.com/r/rust/comments/8a5swr/why_does_hashmaps This commit adds two lines and a comment to the example, to show that the entry object can be re-used after calling get_mut.