David Roman

The reason is that `State` must declare `init(projectedValue: Binding)`. > Property wrappers can enable passing a projected-value argument to a property-wrapped parameter by declaring var projectedValue, and implementing an init(projectedValue:)...

AFAIK that only helps ensure that internal modules aren't visible to consumers, but schemes are still exported because they're included in the `.swiftpm` folder so Xcode sees them regardless of...

@stephencelis I think he's referring to this https://stackoverflow.com/q/69101690 which I've stumbled upon whilst using the nav branch in TCA as well, so yeah I'm pretty sure it's a vanilla SwiftUI...

@stephencelis I appreciate the input. I agree that "data" vs "file" is a question worth exploring.

@tgrapperon hi Thomas. I saw it earlier today, very cool! Thank you for the shoutout in the readme too 😄 I'll close this now that this idea has found a...

This might be a bit out there, but why not one of these: - `ReducerFrom { state, action in ...` - `ReducerWith { state, action in ...` Or even simpler:...

Yes, I'm afraid this is unavoidable because of how `JSONEncoder` is implemented. I'm planning a major release bump that moves away from literal numbers altogether and instead encodes decimals as...

> Here I can only see two possible options, or our back end do the truncate always (or rounding to the nearest), or we change FEBE to use strings instead,...

> I guess an additional `preserve` option to preserve the relative position of the statement as-is might be a good idea? I could definitely use something like that. > You...

If for some reason this issue is due to symlinks and effectively impossible to fix going forward, it might be a good idea to offer an alternate mode of backup...