472 Commits

Author	SHA1	Message	Date
Marijn Haverbeke	5d6a74f020	Only warn about unreachable range patterns when appropriate ... Also simplifies the literal-munging, and moves it into ast_util Closes #1170	2011-11-22 11:49:29 +01:00
Haitao Li	5ca83553bc	rustc: Remove abi from ast::native_mod	2011-11-21 13:49:52 +01:00
Marijn Haverbeke	0c97fcbf66	Properly check kinds in instantiation of generics ... Issue #1177	2011-11-18 12:49:01 +01:00
Marijn Haverbeke	7bef89f9b5	Prevent alias pass from inserting implicit copies for noncopyable types ... Issue #1177	2011-11-18 12:49:01 +01:00
Marijn Haverbeke	17b78c4a7a	Overhaul the kind-checking pass ... Not really useful yet because missing last-use-of-local optimization. Also: instantiation of type parameters needs to be checked. Issue #1177	2011-11-18 12:49:01 +01:00
Marijn Haverbeke	cefff237bf	Make tag, resource and object constructors take their arguments by copy ... Doing something like some([1, 2, 3]) will now no longer create a temporary copy of the vector. It will also be easier for the kind checker to see that putting a resource into a data-structure constructor is safe.	2011-11-18 12:49:01 +01:00
Marijn Haverbeke	9cf48d3753	Preparation for kind system overhaul ... This goes before a snapshot, so that subsequenct patches can make the transition without breaking the build. Disables kind checking pass, makes parser accept both new and old-style kind annotation. Issue #1177	2011-11-18 10:52:28 +01:00
Niko Matsakis	adc79e2f44	remove compile-command from local variable blocks	2011-11-17 11:46:13 -08:00
Brian Anderson	3cc2641fc3	Make various binops not typecheck for unsafe pointers. Closes #1173	2011-11-13 13:55:12 -08:00
Haitao Li	5a7249c935	Cleanup unused imports	2011-11-10 19:19:40 -08:00
Marijn Haverbeke	5b0c103b39	Make it possible to cast unsafe pointers with the 'as' operator	2011-11-02 12:20:12 +01:00
Marijn Haverbeke	7dacccde94	Make shared kind the default only for generic functions ... You almost never want a function with pinned type params. For types, objects, resources, and tags, pinned types are actually often more sane. For most of these, shared rarely makes sense. Only tricky case is objs -- you'll have to think about the kinds you want there. Issue #1076	2011-10-28 17:00:14 +02:00
Matt Brubeck	5d6fe1a533	Remove uint::max/min in favor if math::max/min	2011-10-27 13:37:53 -07:00
Marijn Haverbeke	0ce40f60e7	Drop support for iter, put, and for-each ... Closes #1056	2011-10-21 13:47:24 +02:00
Brian Anderson	9efdd0f326	Merge ast::proto_shared and ast::proto_closure ... Now they are both just proto_shared and proto_shared takes an argument indicating that it is sugared as 'lambda'	2011-10-20 18:23:48 -07:00
Brian Anderson	4b30a06abe	Rename ast::proto_fn to ast::proto_shared	2011-10-20 18:23:48 -07:00
Brian Anderson	29ad3bdb10	Make fn denote a bare function. Convert fn to fn@ as needed	2011-10-20 18:23:48 -07:00
Brian Anderson	391e12124b	Tweak typecheck to enforce covariance on higher-order function arguments	2011-10-20 18:23:48 -07:00
Brian Anderson	8136b92ee8	Give subtype relationships to function types	2011-10-20 18:23:48 -07:00
Brian Anderson	314c011d71	Immutable and mutable? are covariant on their inner types ... Whereas [mutable T] is invariant with respect to T, [T] and [mutable? T] are covariant with respect to T.	2011-10-18 10:37:04 -07:00
Brian Anderson	0f0fa26c72	Enforce variance rules for mutable types	2011-10-17 20:51:34 -07:00
Brian Anderson	48d351b21e	Add a variance transform for calculation of recursive variance	2011-10-17 19:37:34 -07:00
Brian Anderson	d6613384fd	Introduce covariance, contravariance and invariance to the type unifier ... This will be used to resolve some problems with mutable? covariance and also to implement function subtyping	2011-10-17 19:34:12 -07:00
Brian Anderson	b61578e1cd	Don't unify from mutable? to immutable ... Immutable is supposed to be a subtype of mutable-huh.	2011-10-17 16:36:49 -07:00
Brian Anderson	f7a825c614	Split record_var_binding into methods for expected and actual ... This allows unify to maintain the same subtype relationship between expected and actual throughout unify, which we are going to need for mutable? and for function types.	2011-10-17 16:36:49 -07:00
Niko Matsakis	212707ce84	make native functions markable as unsafe and incorporate that ... into the type check	2011-10-12 14:39:34 -07:00
Marijn Haverbeke	b4bae8fea5	Make vectors and strings immediates again ... There's no good reason to force them to be spilled anymore. Some pieces of trans become more elegant this way, and less stack allocs and load/stores are needed. Issue #1021	2011-10-10 15:59:16 +02:00
Marijn Haverbeke	f9fbd86f52	Parse and typecheck by-value and by-ref arg specs ... Add sprinkle && throughout the compiler to make it typecheck again. Issue #1008	2011-10-07 09:09:50 +02:00
Marijn Haverbeke	d243ea57f5	Move last remaining expression types out of trans_expr ... Issue #667	2011-09-29 11:41:45 +02:00
Brian Anderson	b8bb663df7	Don't ever raise unique kinds of pinned kinds to shared (again) ... So *resource, ~resource, [resource] are all pinned. This is counter to the design of the kind system, but this way is a much clearer path to type safety. Once we've established a good baseline with lots of tests, then we can try to make raising pinned kinds work.	2011-09-27 16:03:10 -07:00
Brian Anderson	223f5be166	Unique vectors and boxes of pinned are unique kinds. Closes #977	2011-09-26 13:38:46 -07:00
Graydon Hoare	93f0e9bac3	Refine notes in kind.rs some more. Add a fixme to ty.rs. ... Kinds are still pretty wobbly. See thread starting at https://mail.mozilla.org/pipermail/rust-dev/2011-September/000807.html	2011-09-25 21:20:17 -07:00
Jesse Ruderman	3b5b29c7ec	Reduce and clarify abuse of 'pure' in interner	2011-09-24 16:33:26 -07:00
Jesse Ruderman	064f52fa96	Mark some fns as pure so type_is_unique_box doesn't need to be unchecked	2011-09-24 15:36:09 -07:00
Brian Anderson	856acbf66d	Vectors containing pinned kinds become pinned ... Otherwise they could be copied	2011-09-24 12:36:51 -07:00
Brian Anderson	e5d5682065	Unique pointers containing pinned kinds become pinned ... Issue #409	2011-09-24 12:36:51 -07:00
Brian Anderson	7a76323459	Allow vectors to contain unique boxes. Closes #952 ... Issue #409	2011-09-22 17:00:53 -07:00
Brian Anderson	d174d917e2	Calculate the correct kind for unique boxes ... Issue #409	2011-09-22 15:28:49 -07:00
Brian Anderson	67bac873e0	Add assignment to unique box locals ... Issue #409	2011-09-22 13:53:33 -07:00
Brian Anderson	f6ab12a3b1	Don't unify unique boxes with different mutability ... Issue #409	2011-09-22 11:10:48 -07:00
Brian Anderson	1b3023e4d0	Convert ty::ty_uniq to contain a mutable type ... Issue #409	2011-09-22 10:26:34 -07:00
Brian Anderson	2cc01e2ca2	Add ability to deref unique boxes. Make unique boxes immediates. ... Issue #409	2011-09-21 14:40:55 -07:00
Marijn Haverbeke	eafb6789a2	Stop creating function pairs for static functions ... These are now called directly. When taking their value, a null pointer is added to create a pair.	2011-09-18 22:05:58 +02:00
Tim Chevalier	2b98eccfee	Add a type_is_tup_like predicate that takes a block ctxt, and make some fns pure	2011-09-17 10:18:11 -07:00
Tim Chevalier	1b2c5c4c9b	Make ty_fn_ret pure and get rid of a duplicate function	2011-09-16 13:06:31 -07:00
Marijn Haverbeke	3abe3671bd	Require the parameter that will be referenced to be noted ... Issue #918	2011-09-15 16:15:17 +02:00
Marijn Haverbeke	87fa38910e	Make storing returned references in a by-reference local work ... fn f(a: {x: str}) -> &str { ret a.x; } fn main() { let x = {x: "hi"}; let &y = f(x); // Look ma, no copy! log_err y; } Issue #918.	2011-09-15 15:17:14 +02:00
Marijn Haverbeke	25787bd2b8	Forbid assignment to by-reference bindings ... Issue #918	2011-09-15 14:08:54 +02:00
Marijn Haverbeke	7298b8f4ba	Insert omitted semicolons for statements	2011-09-15 09:49:00 +02:00
Marijn Haverbeke	93de2f0b74	Add syntax and representation for return-by-mutably-rooted-ref ... This will be used in the near future to decide what can safely be done with the returned reference. Issue #918	2011-09-14 17:30:38 +02:00