-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Comparing changes
Open a pull request
base repository: swiftlang/swift
base: main@{1day}
head repository: swiftlang/swift
compare: main
- 11 commits
- 45 files changed
- 5 contributors
Commits on May 30, 2025
-
AST/Sema: Remove code adding
@_spi
to suggested import fix-its.The was never invoked because inaccessibility due to SPI protection level is always diagnosed before missing imports are diagnosed. The functionality could therefore not be tested and should be removed.
Configuration menu - View commit details
-
Copy full SHA for 6ea2dd8 - Browse repository at this point
Copy the full SHA 6ea2dd8View commit details -
AST: Simplify the interface of `DiagnosticEngine::getBestAddImportFix…
…ItLoc()`. For clarity, it should just take a `SourceFile`.
Configuration menu - View commit details
-
Copy full SHA for d258fa7 - Browse repository at this point
Copy the full SHA d258fa7View commit details -
Basic: Fix a bug in LangOptions::hasFeature().
Don't skip checking if a feature is enabled for migration when the feature also has an associated language version.
Configuration menu - View commit details
-
Copy full SHA for 522fee4 - Browse repository at this point
Copy the full SHA 522fee4View commit details -
AST/Sema: Make MemberImportVisibility a migratable feature.
The migration to `MemberImportVisibility` can be performed mechanically by adding missing import declarations, so offer automatic migration for the feature. Resolves rdar://151931597.
Configuration menu - View commit details
-
Copy full SHA for aca6046 - Browse repository at this point
Copy the full SHA aca6046View commit details
Commits on May 31, 2025
-
AST: honour
throws
inAccessorDecl::createImplicit
We would previously unconditionally create the accessor as a throwing accessor irrespective of the parameter. This seems like an oversight and results in an incorrect accessor being formed. This was caught while trying to improve the ClangImporter's handling of aliasing macros.
Configuration menu - View commit details
-
Copy full SHA for 7bece65 - Browse repository at this point
Copy the full SHA 7bece65View commit details
Commits on Jun 1, 2025
-
Add doc comments for some concrete SIMD overloads. (#81890)
Also removed concrete SIMDMask(lowHalf:highHalf:) init, as there is no corresponding generic operation; it was added in error.
Configuration menu - View commit details
-
Copy full SHA for 4007e44 - Browse repository at this point
Copy the full SHA 4007e44View commit details -
Configuration menu - View commit details
-
Copy full SHA for ee41fa5 - Browse repository at this point
Copy the full SHA ee41fa5View commit details -
Configuration menu - View commit details
-
Copy full SHA for d5ef256 - Browse repository at this point
Copy the full SHA d5ef256View commit details -
Configuration menu - View commit details
-
Copy full SHA for 59588bc - Browse repository at this point
Copy the full SHA 59588bcView commit details
Commits on Jun 2, 2025
-
Merge pull request #81894 from hamishknight/fuzzy
[test] Add a few more known type-checker crashers
Configuration menu - View commit details
-
Copy full SHA for f91b4b0 - Browse repository at this point
Copy the full SHA f91b4b0View commit details -
Simd float concrete comparisons (#81892)
There's no reason for these to ever be calls, so they should be transparent instead of just aEIC. Also adds concrete versions of comparisons with scalars, and filecheck tests to make sure these generate 1-2 instruction sequences in release on arm64 (x86_64 is a little trickier to test due to frame pointers, but if we get the right codgen on arm64, in practice we do well on x86_64 for these too). Also makes filecheck patterns for repeating initializers a bit more robust.
Configuration menu - View commit details
-
Copy full SHA for d49dd18 - Browse repository at this point
Copy the full SHA d49dd18View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main@{1day}...main