async

async copied to clipboard

Efficient (non-foundation) async FileSystem helpers

1

Foundation is written synchronously (blocking) and is known to have at least one FS bug now. Specifically for writing files there is no current way to do this asynchronously (from...

Joannis

Separate file reading from Foundation

1

[File](https://github.com/vapor/async/blob/beta/Sources/Async/File/File.swift#L48) is dependent on Foundation file reading which is blocking and dependent on [this line of code](https://github.com/apple/swift-corelibs-foundation/blob/master/Foundation/NSData.swift#L445) which as of today is known to cause infinite loops on 0 length...

Joannis

JavaScript's `Promise` library provides `Promise.try()` as a static method primarily for the purpose of folding error handling of "before the async stuff starts" code into the async model, so that...

gwynne

`EventLoop.current` should be able to return an `EventLoop?` (current EventLoop) stored in the Thread Local Storage

Joannis

Cocoapods support

3

I've found this library to be quite useful for development on iOS projects. Would you mind if I created a podspec with this so it can be used from iOS...

piercifani

ByteParser is useful but isn't as useful as it can be. I suggest splitting it up into more fine grained and specialized parser helper by enforcing splitting up the parser...

Joannis

add and that takes one and two future

4

This PR is to add the "and" syntactic sugar to the future structure. ## Motivations: Often times when working with vapor we have to get futures from multiple places such...

pedantix

flattens any future into void

2

using this in my app to transform any future to void easily and was wondering if you think it could be useful elsewhere ... obviously would add tests if so...

rafiki270

Make it possible to catch specific error types and chain error handling

5

Example: ```swift func getUser(req: Request) -> Future { return User.find(req.parameters.next()).map(to: PublicUser.self) { user in return try user.makePublic() }.catchMap(UserError.self, to: Response.self) { error in guard case .makePublicFailed = error else {...

gwynne

[Beta] Handle errors thrown anywhere in chained Future methods

2

## Summary With Async, it's idiomatic to chain methods. However, in methods that create new Futures (such as Fluent's `Model.save()`), any previous errors thrown seem to be discarded. This means...

bensyverson