224 commits

Author	SHA1	Message	Date
Florian Diebold	6c20d7e979	Small fixes	2020-03-16 18:46:08 +01:00
Florian Diebold	32dce75747	Some more refactoring	2020-03-16 18:38:19 +01:00
Florian Diebold	d6b622cdef	Some cleanup	2020-03-16 18:38:19 +01:00
Florian Diebold	d655749aae	Turn ExpandResult into struct	2020-03-16 18:38:19 +01:00
Florian Diebold	f3c6a2e3db	Fix remaining test failure	2020-03-16 18:38:19 +01:00
Florian Diebold	0660dd10d2	Fix performance problem	2020-03-16 18:38:19 +01:00
Florian Diebold	035db0fbb9	Add test, remove printlns	2020-03-16 18:38:19 +01:00
Florian Diebold	c32529ddd0	Get tests working	2020-03-16 18:38:19 +01:00
Florian Diebold	0f3a54dd4d	wip	2020-03-16 18:38:19 +01:00
Florian Diebold	6305d094ac	Attempt to implement ranking of rules when none matches perfectly (wip)	2020-03-16 18:38:19 +01:00
Florian Diebold	b973158aeb	Make MBE expansion more resilient (WIP)	2020-03-16 18:38:19 +01:00
bors[bot]	beb4f49541	Merge #3513 ... 3513: Completion in macros r=matklad a=flodiebold I experimented a bit with completion in macros. It's kind of working, but there are a lot of rough edges. - I'm trying to expand the macro call with the inserted fake token. This requires some hacky additions on the HIR level to be able to do "hypothetical" expansions. There should probably be a nicer API for this, if we want to do it this way. I'm not sure whether it's worth it, because we still can't do a lot if the original macro call didn't expand in nearly the same way. E.g. if we have something like `println!("", x<|>)` the expansions will look the same and everything is fine; but in that case we could maybe have achieved the same result in a simpler way. If we have something like `m!(<|>)` where `m!()` doesn't even expand or expands to something very different, we don't really know what to do anyway. - Relatedly, there are a lot of cases where this doesn't work because either the original call or the hypothetical call doesn't expand. E.g. if we have `m!(x.<|>)` the original token tree doesn't parse as an expression; if we have `m!(match x { <|> })` the hypothetical token tree doesn't parse. It would be nice if we could have better error recovery in these cases. Co-authored-by: Florian Diebold <flodiebold@gmail.com>	2020-03-09 08:56:58 +00:00
Edwin Cheng	e7206467d5	Add parse_to_token_tree	2020-03-09 00:13:04 +08:00
Florian Diebold	8cc4210278	Add more tests	2020-03-07 15:48:06 +01:00
Edwin Cheng	0563cc8291	fix regression from #3451	2020-03-06 04:32:08 +08:00
Edwin Cheng	6794d50a9b	Fixed whitespace bug	2020-03-04 23:41:14 +08:00
Edwin Cheng	028595548b	Fix #3436	2020-03-04 23:41:14 +08:00
Edwin Cheng	3dc3d9d18f	Fix a bug for single dollar sign macro	2020-03-04 01:03:44 +08:00
Aleksey Kladov	5f8b37563e	Cleanup editing API	2020-02-29 13:51:23 +01:00
Veetaha	5f15e3aeb0	ra_mbe: Remove explicit type annotation	2020-02-22 13:14:46 +02:00
Veetaha	28bdb65407	ra_mbe: added test for malformed token in macro invokation ... There was a panic where lexer returned None on malformed tokens. But now we just ignore tokenization errors in mbe.	2020-02-22 13:10:54 +02:00
Veetaha	93a19bda17	ra_mbe: convert_literal now works with malformed tokens	2020-02-22 13:10:54 +02:00
Shotaro Yamada	d06733efeb	Cleanup	2020-02-19 13:36:59 +09:00
Kirill Bulatov	f6816c253b	Update versions	2020-02-18 16:12:40 +02:00
Kirill Bulatov	eceaf94f19	More manual clippy fixes	2020-02-18 16:12:37 +02:00
Kirill Bulatov	b8ddcb0652	Run cargo +nightly fix --clippy -Z unstable-options	2020-02-18 16:03:08 +02:00
Veetaha	9e7eaa959f	ra_syntax: refactored the lexer design as per @matklad and @kiljacken PR review	2020-02-04 00:00:55 +02:00
Veetaha	ac37a11f04	Reimplemented lexer with vectors instead of iterators	2020-02-04 00:00:55 +02:00
Vincent Rouillé	dc98930965	Add details about test_repeat_bad_var current state	2019-12-30 17:12:20 +01:00
Vincent Rouillé	c670a15345	Details about macro NestingState hit and at_end fields	2019-12-30 17:09:07 +01:00
Vincent Rouillé	6d84dee4e7	fix #2520: change expand_repeat loop stop condition	2019-12-28 22:48:49 +01:00
kjeremy	0d5d63a80e	Clippy lints	2019-12-20 15:14:30 -05:00
Aleksey Kladov	6edc54a1e6	Refactor macro tests	2019-12-19 16:23:23 +01:00
Aleksey Kladov	5c3c2b8690	Fix parsing of interpolated expressions	2019-12-19 14:43:19 +01:00
Edwin Cheng	41544a4088	Refactoring	2019-12-18 13:10:37 +08:00
Edwin Cheng	2ea1cfd780	Rename range to by_kind	2019-12-18 11:36:10 +08:00
Edwin Cheng	e16f3a5ee2	Add test for token map	2019-12-18 11:20:23 +08:00
Edwin Cheng	325532d119	Fix shift id for delim and other tokens	2019-12-18 11:20:23 +08:00
Edwin Cheng	320416d756	Add TokenTextRange	2019-12-18 11:20:22 +08:00
Edwin Cheng	59295854f8	Add token id to delims	2019-12-18 11:20:22 +08:00
Edwin Cheng	aceb9d7fb0	Add token ids for all tt::Leaf	2019-12-18 11:20:22 +08:00
Edwin Cheng	b53587c7bd	Re-export Origin to replace ExpansionOrigin	2019-12-15 01:46:39 +08:00
Edwin Cheng	98f98cbb54	Refactor tt::Delimiter	2019-12-13 21:53:34 +08:00
Florian Diebold	ab4ecca210	Don't wrap most syntax trees in invisible delimiters when converting to token tree ... Otherwise parsing them again doesn't work.	2019-12-05 19:29:39 +01:00
Florian Diebold	18f6a995d0	Add expansion infrastructure for derive macros	2019-12-05 17:23:09 +01:00
Edwin Cheng	bf537eefb5	Fixed mbe trival subtree	2019-11-22 01:02:07 +08:00
Aleksey Kladov	2b6f1ab0e2	Collapse TokenMap and RevTokenMap	2019-11-18 16:08:41 +03:00
Aleksey Kladov	b79d678923	Token-based reverse-mapping	2019-11-18 15:08:39 +03:00
Aleksey Kladov	fd52d721e1	More correct expansion mapping ... We can't really map arbitrary ranges, we only can map tokens	2019-11-17 20:15:55 +03:00
Aleksey Kladov	c8f858d043	Make shift an implementation detail of mbe	2019-11-17 19:11:43 +03:00