8 Commits

Author	SHA1	Message	Date
Vadim Petrochenkov	ab5ba049bc	Partially stabilize RFC 1506 "Clarify relationships between ADTs"	2016-11-08 22:34:05 +03:00
Vadim Petrochenkov	f3b41c18a8	Check fields in union patters/expressions ... Make parsing of union items backward compatible Add some tests	2016-09-03 13:39:34 +03:00
Vadim Petrochenkov	59be332a1b	Remove restrictions from tuple structs/variants ... Hard errors are turned into feature gates	2016-08-13 00:08:14 +03:00
Vadim Petrochenkov	a397b60ebb	Resolve partially resolved paths in struct patterns/expressions ... Treat Def::Err correctly in struct patterns Make instantiate_path and instantiate_type a bit closer to each other	2016-07-08 12:42:57 +03:00
Ariel Ben-Yehuda	91be125899	prevent non-dict-structs from being intialized via FRU ... Fixes #27831	2015-08-15 21:03:10 +03:00
Joshua Yanovski	a71665798b	#8263 part 2: Adding struct name.	2013-10-28 23:51:10 -07:00
Alex Crichton	3585c64d09	rustdoc: Change all code-blocks with a script ... find src -name '*.rs' | xargs sed -i '' 's/~~~.*{\.rust}/```rust/g' find src -name '*.rs' | xargs sed -i '' 's/ ~~~$/ ```/g' find src -name '*.rs' | xargs sed -i '' 's/^~~~$/ ```/g'	2013-09-25 14:27:42 -07:00
Tim Chevalier	db00362313	Make typechecker compositional ... The typechecker previously passed around a boolean return flag to indicate whether it saw something with type _|_ (that is, something it knows at compile-time will definitely diverge) and also had some manual checks for the `ty_err` pseudo-type that represents a previous type error. This was because the typing rules implemented by the typechecker didn't properly propagate _|_ and ty_err. I fixed it. This also required changing expected error messages in a few tests, as now we're printing out fewer derived errors -- in fact, at this point we should print out no derived errors, so report any that you see (ones that include "[type error]") as bugs.	2013-03-20 19:44:38 -07:00