File: strange_interpolation.swift

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (20 lines) | stat: -rw-r--r-- 669 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
 
// Parse-only modes, like swift -parse and SourceKit, should not emit strange
// interpolation errors in `#if swift(>=5)` blocks
// (https://github.com/apple/swift/issues/52343).
//
// Even though this is in the test/SourceKit directory, it also tests
// -frontend -parse behavior because the test cases are exactly the same.

// RUN: %sourcekitd-test -req=open %s -- -swift-version 4.2 %s == -req=print-diags %s | %FileCheck %s
// RUN: %target-swift-frontend -parse -verify -swift-version 4.2 %s

let x = 1

// We should not warn in blocks that can only run when `swift(>=5.0)`.

#if swift(>=5.0)
  print("[\(foo: x)]")
  print("[\(x, x)]")
#endif

// CHECK: <<NULL>>