rust/src/etc/vim/syntax/rust.vim, branch 0.9https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=0.92013-12-27T14:10:11+00:00Renamed ClonableIterator to CloneableIterator2013-12-27T14:10:11+00:00Alexandros Tasossdi1100085@di.uoa.gr2013-12-27T11:53:41+00:00urn:sha1:32c480d63d5f867f44719a83c4f58aa6cec6bea7Rename To{Str,Bytes}Consume traits to Into*.2013-12-14T14:04:22+00:00Chris Morganme@chrismorgan.info2013-12-14T14:04:22+00:00urn:sha1:b76997f3a947b296ca04be184da88ff1c0959dcb
That is:
- `ToStrConsume` → `IntoStr`;
- `ToBytesConsume` → `IntoBytes`.
Vim keyword highlighting improvements.2013-12-10T03:28:27+00:00Chris Morganme@chrismorgan.info2013-12-10T03:28:27+00:00urn:sha1:f39c883598ca937b8b84720f184cdf370daf107d
- Removed the `log` keyword;
- Removed keyword duplicates;
- Highlighted `const` as `Error` rather than `StorageClass`; and
- Highlighted all the reserved keywords as `Error` rather than as
`Keyword`.
(As usual, these highlightings can be overridden if desired.)
Fix up float highlighting in Vim.2013-12-10T03:17:26+00:00Chris Morganme@chrismorgan.info2013-12-10T03:17:26+00:00urn:sha1:3a4d7ff2b9faf8c6861869f0835cfd8abcf47577
This fixes a regression introduced in #10793.
Having a colorscheme which highlights Float the same as Number (I
believe most do), I hadn't noticed that having the special case of "5."
floats (which was one of the added features in #10793) last made it take
precedence, and so it was left to @thestinger to notice it.
The regression meant that in `5.0`, the `5.` was a `rustFloat` (linked
by default to `Float`) and the `0` was a `rustDecNumber` (linked by
default to `Number`), and for `5.0f32` the `5.` was a `rustFloat` and
the `0f32` was a second `rustFloat` (and thus appeared correctly, though
for the wrong reason).
Improve various Vim syntax highlighting things.2013-12-04T01:41:56+00:00Chris Morganme@chrismorgan.info2013-12-04T01:41:56+00:00urn:sha1:c9eed5742e15e8c6ee24376970623a246477b8f0
- Implement comment nesting (the implementation is quite ugly at present
and is not quite correct; note the big comment in that area).
- Highlight invalid escape sequences as errors.
- Fix up various inconsistencies and incorrectnesses in number
highlighting.
- Update prelude items (``std::io::{Buffer, Writer, Reader, Seek}``).
- Highlight the ``proc`` keyword.
- Remove %-formatting sequence highlighting (a relic of old formatting).
- Don't highlight TODO in strings (it's unconventional).
Be more strict about doc comments2013-11-27T23:00:50+00:00Corey Richardsoncorey@octayn.net2013-11-25T04:23:50+00:00urn:sha1:b50b1628840daf849e548c83372f85bc13092314
Previously, `//// foo` and `/*** foo ***/` were accepted as doc comments. This
changes that, so that only `/// foo` and `/** foo ***/` are accepted. This
confuses many newcomers and it seems weird.
Also update the manual for these changes, and modernify the EBNF for comments.
Closes #10638
Grammar error and vim syntax highlighting mistake fixed.2013-11-03T04:34:29+00:00Matt Carberrycarberry.matt@gmail.com2013-11-03T04:34:29+00:00urn:sha1:66abb92a470ae65385e9949cd617d7980c7a2cd9Added octal literal support.2013-11-03T04:26:29+00:00Matt Carberrycarberry.matt@gmail.com2013-11-03T04:26:29+00:00urn:sha1:519b86b8a810e12fe4247c56ffb894579c6b22e7Update prelude items in Vim syntax file.2013-10-29T13:26:25+00:00Chris Morganme@chrismorgan.info2013-10-29T13:26:25+00:00urn:sha1:c20186bde5cc0129e4211fc766f117bf43a4b360Highlight \0 in strings and chars in Vim.2013-10-18T13:56:41+00:00Chris Morganme@chrismorgan.info2013-10-18T13:56:41+00:00urn:sha1:f3796616de78af4153c3adf4be2be68b0ae28865