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
SR-9671 compiler crash: expression has no type / (declref_expr type='' decl=Logging.(file). extension.init(stringLiteral:)
Issue Description:
This is similar to the just opened https://bugs.swift.org/browse/SR-9686 issue however that one causes compilation errors, and this one is about a compiler crash, which looks like this:
The compiler will crash with the error shown above.
Workaround:
Replacing all instances of extension Logging.Metadata.Value with extension Logging.MetadataValue makes the thing compile and work correctly.
// You may need to also remove the public init<T>(stringInterpolationSegment expr: T) {}, though that's fine, and was added a bit too eagerly in there perhaps).
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 7c13f4b8b11ad998b735349fcdc30e3d
duplicates:
Issue Description:
This is similar to the just opened https://bugs.swift.org/browse/SR-9686 issue however that one causes compilation errors, and this one is about a compiler crash, which looks like this:
Which happens on
5.0-DEVELOPMENT-SNAPSHOT-2019-01-16-a
on a fresh checkout of the SSWG proposal for Logging API: https://github.com/weissi/swift-server-logging-api-proposalSpecifically this file: https://github.com/weissi/swift-server-logging-api-proposal/blob/ba9eac90551949f390af0bf8b2866f755460efe4/Sources/Logging/Logging.swift
The problem seems to, same as SR-9686 appear only on Swift 5 (4.2 works well), and seems to be about extensions on type aliases.
To reproduce clone the https://github.com/ktoso/swift-server-logging-api-proposal/tree/boom-repro on the branch boom-repro (which is same as current HEAD of the proposal, but removes the issues that cause https://bugs.swift.org/browse/SR-9686 on line 142).
The compiler will crash with the error shown above.
Workaround:
Replacing all instances of
extension Logging.Metadata.Value
withextension Logging.MetadataValue
makes the thing compile and work correctly.// You may need to also remove the
public init<T>(stringInterpolationSegment expr: T) {
}, though that's fine, and was added a bit too eagerly in there perhaps).The text was updated successfully, but these errors were encountered: