8 commits

Author	SHA1	Message	Date
Andrew Kelley	080dd27157	breaking: fix @typeInfo handling of global error set type ... `builtin.TypeInfo.ErrorSet` is now `?[]Error` instead of `struct{errors:[]Error}`. closes #1936	2019-03-14 11:57:56 -04:00
Andrew Kelley	e402455704	rename std lib files to new convention	2019-03-02 16:46:04 -05:00
Andrew Kelley	5424b4320d	remove namespace type; files are empty structs ... closes #1047	2019-02-28 10:11:32 -05:00
Jimmi HC	d2fb95af88	Fixed std.testing.expectEqual	2019-02-18 17:22:14 +01:00
Andrew Kelley	567c9b688e	Merge pull request #1965 from ziglang/c-pointer-type ... implement C pointers	2019-02-15 02:20:42 -05:00
Andrew Kelley	90b8cd4a45	add C pointer type to @typeInfo ... See #1059	2019-02-11 16:07:40 -05:00
Jimmi HC	2f9fedabf0	testing.expectEqual use expected type as the type of actual ... This allows for impl casts	2019-02-10 12:43:49 +01:00
Andrew Kelley	c2db077574	std.debug.assert: remove special case for test builds ... Previously, std.debug.assert would `@panic` in test builds, if the assertion failed. Now, it's always `unreachable`. This makes release mode test builds more accurately test the actual code that will be run. However this requires tests to call `std.testing.expect` rather than `std.debug.assert` to make sure output is correct. Here is the explanation of when to use either one, copied from the assert doc comments: Inside a test block, it is best to use the `std.testing` module rather than assert, because assert may not detect a test failure in ReleaseFast and ReleaseSafe mode. Outside of a test block, assert is the correct function to use. closes #1304	2019-02-08 18:23:38 -05:00