You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started going through your ignite livestream and deleted the original ignite clone from git and cloned it again. I built ignite without and issues and installed it. I created a new site with the ignite new ExampleSite command without issues. I opened Xcode per the instructions and set my Mac as the destination. I tried a build but got the following...
struct ExampleSite: Site {
var name = "Hello World"
var titleSuffix = " – My Awesome Site"
var url = URL("https://www.example.com")
var builtInIconsEnabled = true
var author = "John Appleseed"
var homePage = Home()
var theme = MyTheme()
}
but the line var url = URL("https://www.example.com") is flagged with the following error. Ambiguous use of 'init(_:)'
I then tried the build in the command line with ignite build in the ExampleSite directory and here are the errors I got.
[257/260] Compiling Ignite resource_bundle_accessor.swift
error: emit-module command failed with exit code 1 (use -v to see invocation)
[258/264] Compiling IgniteStarter Home.swift
[259/264] Compiling IgniteStarter MainTheme.swift
[260/264] Emitting module IgniteStarter
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/Sources/Site.swift:20:15: error: ambiguous use of 'init(:)'
18 | var name = "Hello World"
19 | var titleSuffix = " – My Awesome Site"
20 | var url = URL("https://www.example.com")
| `- error: ambiguous use of 'init(:)'
21 | var builtInIconsEnabled = true
22 |
Foundation.URL:8:12: note: found this candidate in module 'Foundation'
6 | @available(tvOS, introduced: 14.0, deprecated: 16.0, renamed: "init(filePath:)")
7 | @available(visionOS, unavailable, renamed: "init(filePath:)")
8 | public init?(_ path: FilePath)
| `- note: found this candidate in module 'Foundation'
9 | @available(macOS, introduced: 11.0, deprecated: 13.0, message: "Use init?(filePath:directoryHint:) instead")
10 | @available(iOS, introduced: 14.0, deprecated: 16.0, message: "Use init?(filePath:directoryHint:) instead")
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/.build/checkouts/Ignite/Sources/Ignite/Extensions/URL-Unwrapped.swift:13:12: note: found this candidate in module 'Ignite'
11 | /// Creates URLs from static strings, which will only fail if you have made
12 | /// a significant typing error.
13 | public init(_ string: StaticString) {
| - note: found this candidate in module 'Ignite' 14 | if let created = URL(string: String(describing: string)) { 15 | self = created [261/264] Compiling IgniteStarter Site.swift /Users/ppporch/Documents/Hacking with Swift/BrushAndBark/Sources/Site.swift:20:15: error: ambiguous use of 'init(_:)' 18 | var name = "Hello World" 19 | var titleSuffix = " – My Awesome Site" 20 | var url = URL("https://www.example.com") | - error: ambiguous use of 'init(_:)'
21 | var builtInIconsEnabled = true
22 |
Foundation.URL:8:12: note: found this candidate in module 'Foundation'
6 | @available(tvOS, introduced: 14.0, deprecated: 16.0, renamed: "init(filePath:)")
7 | @available(visionOS, unavailable, renamed: "init(filePath:)")
8 | public init?(_ path: FilePath)
| `- note: found this candidate in module 'Foundation'
9 | @available(macOS, introduced: 11.0, deprecated: 13.0, message: "Use init?(filePath:directoryHint:) instead")
10 | @available(iOS, introduced: 14.0, deprecated: 16.0, message: "Use init?(filePath:directoryHint:) instead")
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/.build/checkouts/Ignite/Sources/Ignite/Extensions/URL-Unwrapped.swift:13:12: note: found this candidate in module 'Ignite'
11 | /// Creates URLs from static strings, which will only fail if you have made
12 | /// a significant typing error.
13 | public init(_ string: StaticString) {
| `- note: found this candidate in module 'Ignite'
14 | if let created = URL(string: String(describing: string)) {
15 | self = created
❌ Failed to build.
I know this could be just from the beta 6 of Xcode I am using but wondered if there are changes that will be needed in the future to accomidate Xcode 16.
The text was updated successfully, but these errors were encountered:
I started going through your ignite livestream and deleted the original ignite clone from git and cloned it again. I built ignite without and issues and installed it. I created a new site with the ignite new ExampleSite command without issues. I opened Xcode per the instructions and set my Mac as the destination. I tried a build but got the following...
struct ExampleSite: Site {
var name = "Hello World"
var titleSuffix = " – My Awesome Site"
var url = URL("https://www.example.com")
var builtInIconsEnabled = true
}
but the line var url = URL("https://www.example.com") is flagged with the following error. Ambiguous use of 'init(_:)'
I then tried the build in the command line with ignite build in the ExampleSite directory and here are the errors I got.
[257/260] Compiling Ignite resource_bundle_accessor.swift
error: emit-module command failed with exit code 1 (use -v to see invocation)
[258/264] Compiling IgniteStarter Home.swift
[259/264] Compiling IgniteStarter MainTheme.swift
[260/264] Emitting module IgniteStarter
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/Sources/Site.swift:20:15: error: ambiguous use of 'init(:)'
18 | var name = "Hello World"
19 | var titleSuffix = " – My Awesome Site"
20 | var url = URL("https://www.example.com")
| `- error: ambiguous use of 'init(:)'
21 | var builtInIconsEnabled = true
22 |
Foundation.URL:8:12: note: found this candidate in module 'Foundation'
6 | @available(tvOS, introduced: 14.0, deprecated: 16.0, renamed: "init(filePath:)")
7 | @available(visionOS, unavailable, renamed: "init(filePath:)")
8 | public init?(_ path: FilePath)
| `- note: found this candidate in module 'Foundation'
9 | @available(macOS, introduced: 11.0, deprecated: 13.0, message: "Use init?(filePath:directoryHint:) instead")
10 | @available(iOS, introduced: 14.0, deprecated: 16.0, message: "Use init?(filePath:directoryHint:) instead")
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/.build/checkouts/Ignite/Sources/Ignite/Extensions/URL-Unwrapped.swift:13:12: note: found this candidate in module 'Ignite'
11 | /// Creates URLs from static strings, which will only fail if you have made
12 | /// a significant typing error.
13 | public init(_ string: StaticString) {
|
- note: found this candidate in module 'Ignite' 14 | if let created = URL(string: String(describing: string)) { 15 | self = created [261/264] Compiling IgniteStarter Site.swift /Users/ppporch/Documents/Hacking with Swift/BrushAndBark/Sources/Site.swift:20:15: error: ambiguous use of 'init(_:)' 18 | var name = "Hello World" 19 | var titleSuffix = " – My Awesome Site" 20 | var url = URL("https://www.example.com") |
- error: ambiguous use of 'init(_:)'21 | var builtInIconsEnabled = true
22 |
Foundation.URL:8:12: note: found this candidate in module 'Foundation'
6 | @available(tvOS, introduced: 14.0, deprecated: 16.0, renamed: "init(filePath:)")
7 | @available(visionOS, unavailable, renamed: "init(filePath:)")
8 | public init?(_ path: FilePath)
| `- note: found this candidate in module 'Foundation'
9 | @available(macOS, introduced: 11.0, deprecated: 13.0, message: "Use init?(filePath:directoryHint:) instead")
10 | @available(iOS, introduced: 14.0, deprecated: 16.0, message: "Use init?(filePath:directoryHint:) instead")
/Users/ppporch/Documents/Hacking with Swift/BrushAndBark/.build/checkouts/Ignite/Sources/Ignite/Extensions/URL-Unwrapped.swift:13:12: note: found this candidate in module 'Ignite'
11 | /// Creates URLs from static strings, which will only fail if you have made
12 | /// a significant typing error.
13 | public init(_ string: StaticString) {
| `- note: found this candidate in module 'Ignite'
14 | if let created = URL(string: String(describing: string)) {
15 | self = created
❌ Failed to build.
I know this could be just from the beta 6 of Xcode I am using but wondered if there are changes that will be needed in the future to accomidate Xcode 16.
The text was updated successfully, but these errors were encountered: