about summary refs log tree commit diff
path: root/src/etc/vim/syntax/rust.vim
AgeCommit message (Collapse)AuthorLines
2014-04-18vim: Add StrBuf as type to hilightingRicho Healey-1/+1
2014-03-30Support new attribute syntax in vim syntax fileSteven Fackler-1/+1
2014-03-28Remove `Freeze` and add `Share` in vim's syntaxFlavio Percoco-1/+1
2014-03-28Rename Pod into CopyFlavio Percoco-1/+1
Summary: So far, we've used the term POD "Plain Old Data" to refer to types that can be safely copied. However, this term is not consistent with the other built-in bounds that use verbs instead. This patch renames the Pod kind into Copy. RFC: 0003-opt-in-builtin-traits Test Plan: make check Reviewers: cmr Differential Revision: http://phabricator.octayn.net/D3
2014-03-20rm obsolete references to `DeepClone`Daniel Micay-1/+1
2014-03-13std: Rename Chan/Port types and constructorAlex Crichton-1/+1
* Chan<T> => Sender<T> * Port<T> => Receiver<T> * Chan::new() => channel() * constructor returns (Sender, Receiver) instead of (Receiver, Sender) * local variables named `port` renamed to `rx` * local variables named `chan` renamed to `tx` Closes #11765
2014-03-01Merge pull request #12308 from kballard/vim-nested-commentsbors-5/+6
vim: Tweak how comment nesting works Reviewed-by: brson
2014-02-27Update Vim syntax file last change date.Chris Morgan-1/+1
2014-02-27Update prelude items in Vim syntax.Chris Morgan-20/+9
2014-02-27Downgrade `do` to a reserved keyword in Vim.Chris Morgan-2/+2
This means it gets highlighted as Error by default.
2014-02-27Highlight the `mod` in `extern mod x;` as Error.Chris Morgan-1/+3
Just like the bare keyword `crate` is highlighted as Error (a little dubious, actually, given macros), `mod` is invalid after `extern`: it's obsolete syntax.
2014-02-24vim: Tweak how comment nesting worksKevin Ballard-5/+6
Don't try to match line comments inside of a comment block. That makes no sense and can highlight differently for people who override their highlights. Similarly, don't match a doc-comment inside of a comment block. It shouldn't be highlighted differently unless it's actually a doc-comment (and nested comments are obviously not doc comments). Fixes #12307.
2014-02-24Transition to new `Hash`, removing IterBytes and std::to_bytes.Huon Wilson-1/+0
2014-02-22Move std::num::Integer to libnumBrendan Zabarauskas-1/+1
2014-02-17auto merge of #12321 : bjz/rust/remove-real, r=alexcrichtonbors-1/+1
This is part of the effort to simplify `std::num`, as tracked in issue #10387. It is also a step towards a proper IEEE-754 trait (see #12281).
2014-02-17Remove Real trait and move methods into FloatBrendan Zabarauskas-1/+1
This is part of the effort to simplify `std::num`, as tracked in issue #10387.
2014-02-17Remove CloneableTuple and ImmutableTuple traitsBrendan Zabarauskas-4/+0
These are adequately covered by the Tuple2 trait.
2014-02-14Add CheckedDiv to vim syntaxKevin Ballard-1/+1
2014-02-14Update vim syntax for extern crateKevin Ballard-2/+9
2014-02-07Delete send_str, rewrite clients on top of MaybeOwned<'static>Kevin Ballard-2/+1
Declare a `type SendStr = MaybeOwned<'static>` to ease readibility of types that needed the old SendStr behavior. Implement all the traits for MaybeOwned that SendStr used to implement.
2014-01-29auto merge of #11672 : bjz/rust/remove-times, r=brsonbors-1/+0
`Times::times` was always a second-class loop because it did not support the `break` and `continue` operations. Its playful appeal (which I liked) was then lost after `do` was disabled for closures. It's time to let this one go.
2014-01-30Remove Times traitBrendan Zabarauskas-1/+0
`Times::times` was always a second-class loop because it did not support the `break` and `continue` operations. Its playful appeal was then lost after `do` was disabled for closures. It's time to let this one go.
2014-01-28Rename CopyableTuple to CloneableTupleVirgile Andreani-1/+1
2014-01-28Rename ImmutableCopyableVector to ImmutableCloneableVectorVirgile Andreani-1/+1
2014-01-28Rename OwnedCopyableVector to OwnedCloneableVectorVirgile Andreani-1/+1
2014-01-28Rename CopyableVector to CloneableVectorVirgile Andreani-1/+1
2014-01-27As Either no longer exists, remove Either, Left, and Right from syntax filesScott Lawrence-3/+0
2014-01-18auto merge of #11311 : hdima/rust/vim-syntax-spell-check, r=cmrbors-7/+7
Add `@Spell` clusters to Vim syntax highlighting file to do spell checking only inside comments and strings
2014-01-16Merge Bitwise and BitCount traits and remove from prelude, along with BoundedBrendan Zabarauskas-2/+1
One less trait in std::num, and three less exported in the prelude.
2014-01-09Remove ApproxEq and assert_approx_eq!Brendan Zabarauskas-1/+1
This trait seems to stray too far from the mandate of a standard library as implementations may vary between use cases.
2014-01-04Add @Spell clusters to Vim syntax fileDmitry Vasiliev-7/+7
Add @Spell clusters to Vim syntax highlighting file to do spell checking only inside comments and strings
2013-12-27Renamed ClonableIterator to CloneableIteratorAlexandros Tasos-1/+1
2013-12-15Rename To{Str,Bytes}Consume traits to Into*.Chris Morgan-2/+2
That is: - `ToStrConsume` → `IntoStr`; - `ToBytesConsume` → `IntoBytes`.
2013-12-10Vim keyword highlighting improvements.Chris Morgan-5/+7
- 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.)
2013-12-10Fix up float highlighting in Vim.Chris Morgan-5/+6
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).
2013-12-04Improve various Vim syntax highlighting things.Chris Morgan-36/+42
- 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).
2013-11-27Be more strict about doc commentsCorey Richardson-2/+2
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
2013-11-02Grammar error and vim syntax highlighting mistake fixed.Matt Carberry-1/+1
2013-11-02Added octal literal support.Matt Carberry-1/+5
2013-10-30Update prelude items in Vim syntax file.Chris Morgan-22/+20
2013-10-19Highlight \0 in strings and chars in Vim.Chris Morgan-3/+3
2013-10-19Update prelude items in Vim syntax.Chris Morgan-6/+8
2013-10-08add vim syntax highlighting support for raw string literalsBenjamin Herr-0/+1
2013-09-26Add 'continue' keyword to emacs, vim, gedit, kateBrian Anderson-1/+1
2013-09-22Reserve the `alignof`, `offsetof`, and `sizeof` keywordsBirunthan Mohanathas-1/+1
Closes #9333.
2013-09-22Remove 'copy' from syntax files, as it's no longer a keywordScott Lawrence-2/+1
2013-09-04Update highlighting for prelude changes.Chris Morgan-2/+2
2013-09-04Highlight everything in the prelude in Vim.Chris Morgan-26/+78
This is a rather more extensive change than the last, but *ever* so much easier to maintain reasonably, as there's then something to track directly.
2013-09-04Update a handful of keywords highlighted in Vim.Chris Morgan-8/+6
I added a few and removed a few and corrected a couple, all with reference to the prelude. It ends up a slightly arbitrary decision precisely what ends up in and what doesn't, unfortunately.
2013-09-04Modernise some Vim syntax highlighting.Chris Morgan-3/+5
- Remove highlighting of ``L"..."`` (obsolete syntax) - Remove backslash at end of line being a line continuation always (obsolete syntax; this only affects comments, actually) - Add highlighting for backslash at end of line and leading whitespace on the following line inside a string (a genuine line continuation)
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-18 12:41:35 +0000