Skip to content

Commit a4a786c

Browse files
committed
Don’t use unsafeFlags when building SwiftSyntax
The group info file was only being used when building SwiftSyntax as part of the toolchain. But nobody should be using SwiftSyntax from the toolchain, so it wasn’t providing any value. Exclusivity checking is no longer a performance problem, so there’s no reason to disable it anymore.
1 parent 49b3bbd commit a4a786c

File tree

2 files changed

+1
-80
lines changed

2 files changed

+1
-80
lines changed

Package.swift

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,8 @@ import Foundation
77
/// to speed up the build or improve it.
88
var swiftSyntaxSwiftSettings: [SwiftSetting] = []
99
if ProcessInfo.processInfo.environment["SWIFT_BUILD_SCRIPT_ENVIRONMENT"] != nil {
10-
let groupFile = URL(fileURLWithPath: #file)
11-
.deletingLastPathComponent()
12-
.appendingPathComponent("utils")
13-
.appendingPathComponent("group.json")
1410
swiftSyntaxSwiftSettings += [
15-
.define("SWIFTSYNTAX_ENABLE_ASSERTIONS"),
16-
.unsafeFlags([
17-
"-Xfrontend", "-group-info-path",
18-
"-Xfrontend", groupFile.path,
19-
// Enforcing exclusivity increases compile time of release builds by 2 minutes.
20-
// Disable it when we're in a controlled CI environment.
21-
"-enforce-exclusivity=unchecked",
22-
]),
11+
.define("SWIFTSYNTAX_ENABLE_ASSERTIONS")
2312
]
2413
}
2514
if ProcessInfo.processInfo.environment["SWIFTSYNTAX_ENABLE_RAWSYNTAX_VALIDATION"] != nil {

utils/group.json

Lines changed: 0 additions & 68 deletions
This file was deleted.

0 commit comments

Comments
 (0)