11 commits

Author	SHA1	Message	Date
Aleksey Kladov	b56e020077	Apply couple of rule of thumbs to simplify highlighting code ... Main one: instead of adding a parameter to function to handle special case, make the caller handle it. Second main one: make sure that function does a reasonable thing. `highlight_def` picks a color for def, *regardless* of the context the def is use. Feeding an info from the call-site muddies the responsibilities here. Minor smells, flagging the function as having space for improvement in the first place: * many parameters, some of which are set as constants on most call-sites (introduce severalfunction instad) * boolean param (add two functions instead)	2020-08-19 17:53:41 +02:00
Aleksey Kladov	11a1bb1c3e	Inline trivial function	2020-08-19 17:41:56 +02:00
Aleksey Kladov	a9778c6d73	Simplify	2020-08-19 17:37:19 +02:00
Aleksey Kladov	0b62b990ba	Minor	2020-08-19 17:33:25 +02:00
Aleksey Kladov	422ac441c2	Minor cleanups	2020-08-19 17:31:26 +02:00
Aleksey Kladov	5da1dc9a8b	Better name	2020-08-19 17:30:43 +02:00
Aleksey Kladov	61754678fb	Better API factoring around self access modes	2020-08-19 17:02:50 +02:00
Aleksey Kladov	b9b4693ce3	Add SelfParam to code_model	2020-08-19 15:16:24 +02:00
Paul Daniel Faria	3456e2eec7	Add new method to Semantics, method_receiver_kind, which returns the kind of self ... The options are Shared, Mutable, Consuming, and Copied. Use this to add proper highlighting to methods based on usage.	2020-08-16 10:26:16 -04:00
Paul Daniel Faria	a044ff0138	Mark mutating functions with mutable modifier, and owning functions with consuming.	2020-08-16 10:22:51 -04:00
Aleksey Kladov	1b0c7701cc	Rename ra_ide -> ide	2020-08-13 17:58:27 +02:00

Renamed from crates/ra_ide/src/syntax_highlighting.rs (Browse further)