Stephen Celis

@stephencelis

Working on @pointfreeco and @isowords. 🦋 @stephencelis.com 🐘 @[email protected]

California

stephencelis.com

Replies Reposts Media

Stephen Celis
@stephencelis
17h
If you’re interested in writing async code that is easy and reliable to test, and free of UI glitches from thread hops, nonisolated(nonsending) and Task.immediate can get you there!
Point-Free
@pointfreeco
20h
We tried using two modern Swift concurrency tools to allow us to embrace non-sendability: • nonisolated(nonsending) • Task.immediate They got us close to our goals, but sadly there were still data races. Watch this week's episode to understand why: pointfree.co/episodes/ep381…
Stephen Celis
@stephencelis
Aug 4
We’re constantly impressed with the ergonomics and safety Swift features like macros and key paths unlocks. I’m not aware of another SQL library out there that remains type-safe over the JSON data in a column 😁
Point-Free
@pointfreeco
Aug 4
SQLiteData has brand new type-safe and schema-safe JSON APIs by way of the StructuredQueries library. Extract, update, and query directly over JSON (and JSONB!) column data without fear of stringly-typed runtime errors. pointfree.co/blog/posts/220…
1
Stephen Celis
@stephencelis
Apr 3
Take it from our personal experience: you do NOT want to throw “Sendable” on just any type!
Point-Free
@pointfreeco
Apr 3
Sendability errors in Swift might make you wonder if you should be adding “Sendable” to all your types. It seems innocent enough, and don’t we want all our types to be concurrency-safe? The answer: an emphatic NO! Take great care making a type sendable 👇
3
Stephen Celis
@stephencelis
Mar 5
These tools really do feel like magic to work with. You describe your features and how they should work, and you get an incredible feedback loop (for human or agent alike!) to something that just works.
Point-Free
@pointfreeco
Mar 5
Replying to @pointfreeco
And all of TCA’s powerful testing tools just work! You play a script of user actions to your feature and get to exhaustively test how your feature changes over time by describing it in simple mutations:
Stephen Celis
@stephencelis
Feb 27
It’s not possible in a generic/static way, but you can run an actor on a specific actor dynamically at runtime by overriding its unowned serial executor. One of the many things we cover in our videos!
Brian Semiglia
@BrianS_
Feb 27
Replying to @stephencelis
Is it possible for a type to declare itself an actor and then have instances declare what kind?