10 Commits (a35ea15442500f69cb607923c3ec5d0fb7fa8d52)

Author	SHA1	Message	Date
Andrew Paseltiner	703285826a	Correct spelling in docs	8 years ago
Jeehoon Kang	d787bec7d5	Revise TARPL's description for allocating 0 bytes ... In Section 3.2, TARPL says that "standard allocators (including jemalloc, the one used by default in Rust) generally consider passing in 0 for the size of an allocation as Undefined Behaviour." However, the C standard and jemalloc manual says allocating zero bytes should succeed: - C11 7.22.3 paragraph 1: "If the size of the space requested is zero, the behavior is implementation-defined: either a null pointer is returned, or the behavior is as if the size were some nonzero value, except that the returned pointer shall not be used to access an object." - [jemalloc manual](http://www.freebsd.org/cgi/man.cgi?query=jemalloc&sektion=3): "The malloc and calloc functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned and errno is set to ENOMEM." + Note that the description for `allocm` says "Behavior is undefined if size is 0," but it is an experimental API.	8 years ago
Alexis Beingessner	42582a28ed	frob emphasis	8 years ago
Alexis Beingessner	fadf50dc7d	many many pnkfelix fixes	8 years ago
Alexis Beingessner	42629127a0	mention void pointers	8 years ago
Alexis Beingessner	7415230ad1	flesh out void types	8 years ago
Alexis Beingessner	dae4f5665c	fix typo	8 years ago
Alexis Beingessner	4b9d71becf	nits and realigning	8 years ago
Alexis Beingessner	9e8b997dd0	void types	8 years ago
Alexis Beingessner	c6c64270bf	SHARD ALL THE CHAPTERS	8 years ago