NetNewsWire/Articles
Joe Heck 8df105aad4 replacing os_unfair_lock with NSLock
learned that os_unfair_lock with & was quite unsafe when used within
swift. Apparently in swift, &foo in Swift means "make a copy of foo and
pass it inout to a function, then overwrite its value with whatever
the function did to it when that function returns."

And if you're using it within a struct, it's apparently even more
dangerous. because the address of self can change from call to call
— self might not even have an address, it might be contained in
registers only.

Using NSlock will be a smidge less performant, but notably more safe.
2021-05-10 11:14:04 -07:00
..
.swiftpm/xcode/xcshareddata/xcschemes Convert Account into a Swift Package 2020-07-30 07:27:14 -05:00
Sources/Articles replacing os_unfair_lock with NSLock 2021-05-10 11:14:04 -07:00
.gitignore Convert Articles, ArticlesDatabase, and SyncDatabase to Swift Packages 2020-07-30 04:54:21 -05:00
Package.swift Update to the latest RSCore 2021-02-07 20:26:30 -06:00
README.md Convert Articles, ArticlesDatabase, and SyncDatabase to Swift Packages 2020-07-30 04:54:21 -05:00

Articles

A description of this package.