issues Search Results · repo:swiftlang/swift-syntax language:Swift
Filter by
453 results
(69 ms)453 results
inswiftlang/swift-syntax (press backspace or delete to remove)The following test case crashes the parser:
a a a
SwiftParser/StringLiterals.swift:181: Fatal error: The lexer should only add trailing trivia to a string segment if the newline is escaped by ...
hamishknight
- Opened on Jun 24
- #3113
Issue Kind
None
Source Code
struct S: @unsafe nonisolated P {}
struct S: @preconcurrency nonisolated P {}
Description
The opposite order of annotations is rejected by both parsers, which may also ...
bug
SwiftParser
AnthonyLatsis
- 1
- Opened on Jun 19
- #3109
Description
The MemberAttributeMacro does not get invoked for members that are inside #if guards.
Steps to Reproduce
Looking at the unit tests, I can add a new one to the MemberAttributeMacroTests: ...
bug
jaredgrubb
- 1
- Opened on Jun 18
- #3106
The following test case crashes the new parser:
{ a: (a $
0 swift-frontend 0x0000000109d88934 llvm::sys::PrintStackTrace(llvm::raw_ostream , int) + 56
1 swift-frontend ...
SwiftParser
hamishknight
- Opened on Jun 16
- #3103
A missing version marker module leads to very confusing behavior. Add a test to make sure that all release tags have a
corresponding module in the GitHub action.
bnbarham
- Opened on Jun 16
- #3101
I ve been updating a couple of libraries that support a wide range of SwiftSyntax versions using the #if
canImport(SwiftSyntaxMarkerModule) method to work around breaking API changes. These packages cannot ...
scottrhoyt
- 5
- Opened on Jun 12
- #3099
The following crashes the new parser:
#sourceLocation \(
SwiftParser/StringLiterals.swift:346: Fatal error: String segment produced by the lexer should not have unexpected text or trivia because ...
hamishknight
- Opened on Jun 9
- #3097
Description
Please, refer to this minimal reproducible project.
Steps to Reproduce
In the minimal reproducible project the issue is reproduced already 🙂
bug
RoBo-Inc
- 1
- Opened on Jun 6
- #3094
I ve got some use cases for macros where I end up producing an expansion that calls other macros, and those other macros
may produce diagnostics. Right now, they end up pointing to the temporary file containing ...
Macros
grynspan
- 1
- Opened on May 26
- #3085
Description
We ought to have a common protocol for try, await, and unsafe expression nodes, which would allow us to simplify the
checks added in #3037.
enhancement
hamishknight
- 2
- Opened on Apr 3
- #3040

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.