Comments (3)
I have a series of patches that I hope to finish uploading soon. That at least makes the test suite build; there are a few failures and one of them is particularly worrisome (assertion failure in FilePath).
from swift-system.
The test suite in this package is currently completely broken on Windows.
Is this why Windows is not currently part of the PR checks for this repo? That seems to me like the most obvious near-term way to avoid breaking the Windows port. Also, until Windows is part of the regular PR checks, it seems to me like there should be some notes in the documentation about what the status of this project is with respect to Windows.
That might take the form of:
- Elaborating in the README on how close swift-system is to the "vision" described of being the home for system interfaces "for all supported Swift platforms"βis Windows currently considered a supported platform for swift-system?
- Explicitly noting in the README that there is a lower stability guarantee for Windows than there is for other platforms, and encourage users on Windows to pin to a specific release
- Describing in CONTRIBUTING.md exactly what the expectations are with respect to testing that the Windows port
from swift-system.
Scheduling for 1.4.0; I think it's time to do this.
from swift-system.
Related Issues (20)
- FilePath is Decodable, but not from a String
- Deprecated APIs are lacking availability information HOT 2
- Trunk compilation is broken with the Swift 5.7 compiler on linux HOT 1
- Release package version 1.4.0
- Assertion failure in FilePathParsing.swift HOT 3
- Build fails in release with: ld: Undefined symbols: static (extension in SystemPackage):SystemPackage._StrSlice.== infix(A, A) -> Swift.Bool HOT 1
- Update README for 1.4.0
- Release Testing for 1.4.0 HOT 2
- Does not compile for visionOS
- Fix `SystemString`'s `Collection` conformance
- strerror is not (guaranteed) to be thread safe HOT 1
- Ship a quick interim 1.3.0 update resolving platform support issues HOT 12
- Should `FileDescriptor.closeAfter` provide a `FileDescriptor` to the invoked closure?
- Add `FileDescriptor.openPipe`
- Add System.FilePath <-> SystemPackage.FilePath conversion?
- API Request: Splitting `POSIXPath` and `WindowsPath` out of `FilePath` HOT 2
- POSIX Spawn APIs HOT 1
- FileDescriptor.open(_:_:options:permissions:retryOnInterrupt:) should print an error message when trapping on unspecified permissions HOT 1
- Windows build is broken HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swift-system.