4 ms·
I spent some time with Swift-on-the-server last year and definitely felt like the class/struct difference made sense. But I have to agree, from a novice eye at
by cdcarter 3y ago
I spent some time with Swift-on-the-server last year and definitely felt like the class/struct difference made sense.
But I have to agree, from a novice eye at least, result builders look to be a feature added to support SwiftUI and limited other use cases. Have you seen many examples of third party libraries successfully using them?
And while we're here, do the introduction of macros in Swift 5.9 allow room for replacing result builders with something more uniformly useful?
- jurip 3y agoResult builders are pretty popular in third party libraries, too. There's good use of them in Pointfree's libraries Parsing (https://github.com/pointfreeco/swift-parsing https://github.com/pointfreeco/swift-parsing) and Composable Architecture (https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/migratingtothereducerprotocol/ https://pointfreeco.github.io/swift-composable-architecture/...). A quick search in the package index also finds things like these: - https://swiftpackageindex.com/davidcaddy/DCSettings https://swiftpackageindex.com/davidcaddy/DCSettings - https://swiftpackageindex.com/tdeleon/relax/2.1.0/documentation/relax/definingrequests https://swiftpackageindex.com/tdeleon/relax/2.1.0/documentat... - https://swiftpackageindex.com/mkj-is/PathBuilder https://swiftpackageindex.com/mkj-is/PathBuilder - https://swiftpackageindex.com/Saelyria/Artemis https://swiftpackageindex.com/Saelyria/Artemis - https://swiftpackageindex.com/FluidGroup/MondrianLayout https://swiftpackageindex.com/FluidGroup/MondrianLayout etc.