I apologize in advance if I'm missing something obvious, but I've been unable to figure this out on my own. If, for example, I have:

// foo.swift
class Foo {}

and

// bar.swift
let foo = Foo()

where foo.swift and bar.swift are in the same target, it complains that it doesn't recognize Foo when Foo is used in bar.swift. How do I configure this plugin to see other modules in the same target?

This is a massive change to how indentation works. This removes the previous function and replaces it with a new one. Originally I wanted to rely on cindent more here but after spending some time with it, it really isn't right for swift. Still, falling back to it is better than handling all of the cases. This could still use some massive refactoring but I want it to get tested a little first.

It'll be nice to set up ctags with this plugin. But I'm not familiar with Vim plugin dev.

Here is my .ctags config:

--langdef=Swift 
--langmap=Swift:+.swift 
--regex-swift=/enum[ \t]+([^\{\}]+).*$/\1/n,enum,enums/ 
--regex-swift=/typealias[ \t]+([^:=]+).*$/\1/t,typealias,typealiases/ 
--regex-swift=/protocol[ \t]+([^:\{]+).*$/\1/p,protocol,protocols/
--regex-swift=/struct[ \t]+([^:\{]+).*$/\1/s,struct,structs/ 
--regex-swift=/class[ \t]+([^:\{]+).*$/\1/c,class,classes/ 
--regex-swift=/func[ \t]+([^\(\)]+)\([^\(\)]*\)/\1/f,function,functions/ 
--regex-swift=/(var|let)[ \t]+([^:=]+).*$/\2/v,variable,variables/ 
--regex-swift=/^[ \t]*extension[ \t]+([^:\{]+).*$/\1/e,extension,extensions/

And .vimrc:

" tagbar
nmap <F8> :TagbarToggle<CR>
let g:tagbar_type_swift = {
  \ 'ctagstype': 'swift',
  \ 'kinds' : [
    \ 'n:Enums',
    \ 't:Typealiases',
    \ 'p:Protocols',
    \ 's:Structs',
    \ 'c:Classes',
    \ 'f:Functions',
    \ 'v:Variables',
    \ 'e:Extensions'
  \ ],
  \ 'sort' : 0
\ }

Here is how it looks like:

This adds the new (introduced in Swift 2) @available and #available attributes to the swift syntax file.

I chose to add this to the new swiftConditionalAttribute (since it's a conditional attribute that is used in if/guard statements) rather than the existing swiftAttributes (which are typically used to apply to functions/classes).

If you think that's wrong, I can easily update this.

Resolves #54

Try indenting:

  override func observeValueForKeyPath(keyPath: String!,
                                       ofObject object: AnyObject!, 
                                       change: NSDictionary!, 
                                       context: CMutableVoidPointer) {
    println("CHANGE OBSERVED: \(change)")
  }

Result:

  override func observeValueForKeyPath(keyPath: String!,
                                       ofObject object: AnyObject!, 
                                                change: NSDictionary!, 
                                                        context: CMutableVoidPointer) {
                                                          println("CHANGE OBSERVED: \(change)")
                                                        }

SourceKit can now be built under Linux out of the box.

Have you though about using it (via SourceKitten or directly?) not only for autocompletion, but also for syntax highlighting? Or may be there are reasons to avoid it?

Hi! Thanks for this awesome vim plugin. Color syntax's works pretty well but I'm facing indentation issues. Take as an example the code below.

enum Pepper {                                                                                                                                                   
    case Paprika, RedPepper, HabaneroChili, KomodoDragonChiliPepper
}

func heatUnits(pepper: Pepper) -> String {
    switch pepper {
    case .Paprika:
        return "🔥" 
    case .RedPepper:
        return "🔥🔥🔥🔥"
    case .HabaneroChili:
        return "🔥🔥🔥🔥🔥🔥🔥"
    case .KomodoDragonChiliPepper:
        return "🔥🔥🔥🔥🔥🔥🔥🔥🔥"
}

when I ident it gg=G it becomes:

enum Pepper {                                                                                                                                                   
case Paprika, RedPepper, HabaneroChili, KomodoDragonChiliPepper
}

func heatUnits(pepper: Pepper) -> String {
switch pepper {
case .Paprika:
return "🔥"
case .RedPepper:
return "🔥🔥🔥🔥"
case .HabaneroChili:
return "🔥🔥🔥🔥🔥🔥🔥"
case .KomodoDragonChiliPepper:
return "🔥🔥🔥🔥🔥🔥🔥🔥🔥"
}

Am I missing something? I'm using the El Capitan's VIM:

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Apr  5 2016 14:53:37)
Compiled by [email protected]

Thank you!

So, a fun task is running gg=G on every Swift file and seeing what happens…

UIView.animateWithDuration(0.4, animations: {
                           view.backgroundColor = UIColor.redColor()
})

I see this style was decided on in #19, but personally I prefer wrapping multiline function calls like this:

someFunction(with: 1, a: 2, lot: 3, of: 4, parameters: 5,
    objectiveCPrefersLengthyExternalParameterNames: true)

because it's lessing jarring to my eyes, and also because Objective-C APIs don't play well with the "Python" style. Would this fix the closure issue?

"The Basics" chapter of the official "The Swift Programming Language" book states that you can pad numbers with underscores to help readability.

This commit also handles the case where underscore padded numbers can also contain a period (i.e., underscore padded float/double)

Additionally, added some underscore padded numbers in example/swift.vim for testing purposes.

Fixes #51

Curly braces are not un-indenting correctly for me. It comes out like this:

        if(true){
            }else{
                }

I would expect it to be like this

        if(true){
        }else{
        }

I have tried enabling cindent, autoindent, and smartindent. Doesn't seem to have any effect

ftplugin/swift.vim includes ? and ! as keywords: setlocal iskeyword+=?,!,@-@,#

which makes optional types different from the non-optional version. So if I place the cursor over UICollectionView in the line for v1 and hit keys like gd, or *, it doesn't match the lines for v2 and v3. Vice versa.

var v1: UICollectionView
var v2: UICollectionView?
var v3: UICollectionView!

Seems better to set keywords like so: setlocal iskeyword+=@-@,#

Any reason why ! and ? are included?

The following Swift file

switch readLine() {
case "1": print("1")
case "2":
print("2")
case "a": 
switch readLine() {
case "1": print("1")
default: print("Other")
}
default: print("Other")
}

(there is whitespace in "a":) is indented like so

switch readLine() {
    case "1": print("1")
case "2":
    print("2")
    case "a": 
    switch readLine() {
        case "1": print("1")
        default: print("Other")
    }
    default: print("Other")
}

The expected behavior is for it to be indented as so:

switch readLine() {
case "1": print("1")
case "2":
    print("2")
case "a": 
    switch readLine() {
    case "1": print("1")
    default: print("Other")
    }
default: print("Other")
}

The detection for cases appears to expect the : to end the line, which is not required by Swift, and it appears to align a case with the previous use of switch instead of the switch it is actually part of. The syntax highlighting still appears correct.

This is working:

init(t: type, f: @escaping () -> String)

@escaping is completely highlighted as swiftAttributes.

This is not working:

init(t: Type, f: @escaping () -> String)

@ is highlighted as swiftAttributes, escaping is highlighted as swiftInterpolatedString

(Same goes for functions instead of inits)

I just installed swift.vim in neovim 0.4.3. My swift files compile and run fine in Swift version 5.3-dev (LLVM 55d27a5828, Swift 6a5d84ec08).

But vim doesn't find any folds in my swift files. When I press one of the commands to open or close folds, such as zO or zc, I see the error E490: No fold found. This is unusual. Most languages have code folding support in vim.

I'm new to swift so I'm not familiar with how things are supposed to work. Is there a way to get syntax errors to show up when editing a standalone file?

Similarly, if I edit a file that's part of an xcode project, is there a way to get syntax errors to display?

So far, I've only gotten this to work after init'ing a package and then editing Source/package/main.swift

Previously, certain keywords in comments would be left unmatched if the docstring was written as multiple single-line comments or if the comments began with an asterisk. For example:

/**
 * Function description
 * - Parameter a: parameter description
 * - Returns: return value description
 */

or

/// Function description
/// - Parameter a: parameter description
/// - Returns: return value description

This pull request fixes that, and furthermore introduces two new syntax groups: swiftDocStringParam, which matches parameter names in docstrings, and swiftDocStringInlineCode which matches text surrounded by back-ticks in comments. Those two groups are highlighted with SpecialComment by default, but by overriding them users should be able to get closer to the way Xcode displays comments.

Below is a screenshot with the improved highlighting: Note how - Returns and - Parameter are highlighted in bold, and the parameter name and the zero in the last line are highlighted in a lighter colour.