David Smith
I am an irregular collection of floating diffuse lights, chiming softly
Posts
I am an irregular collection of floating diffuse lights, chiming softly
I am an irregular collection of floating diffuse lights, chiming softly
I am an irregular collection of floating diffuse lights, chiming softly
I am an irregular collection of floating diffuse lights, chiming softly
"average person writes 3 UTF16 decoders a year" factoid actualy just statistical error. average person writes 0 decoders per year. Unicodes Smith, who lives in cave & has two in the same open PR, is an outlier adn should not have been counted
I am an irregular collection of floating diffuse lights, chiming softly
I am an irregular collection of floating diffuse lights, chiming softly
I wrote up a little flowchart here for how I think about "is it ok to do this work on the default Swift Concurrency thread pool?": https://forums.swift.org/t/is-concurrent-now-the-standard-tool-for-shifting-expensive-synchronous-work-off-the-main-actor/82976/17
When to make something asynchronous, when to make it parallel, and how parallel to make it are all inherently tricky in extremis, but the default behavior is the default for a reason, and is appropriate in the vast majority of cases.
I am an irregular collection of floating diffuse lights, chiming softly
I am an irregular collection of floating diffuse lights, chiming softly
If you, like me, have ever been annoyed at the wastefulness of allocating a whole Array or Set just to store one object to pass to something:
1: change the thing you're passing it to from [Foo] to some Collection<Foo> or some RandomAccessCollection<Foo>
2: replace your Array with a CollectionOfOne
No allocations, no refcounting, no indirection :)