-
Notifications
You must be signed in to change notification settings - Fork 118
Fix Sendable checking
#240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Can one of the admins verify this patch? |
11 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
I have only added necessary |
d602fa3 to
7f19403
Compare
|
@swift-server-bot test this please |
Current state:
We’re waiting for
SwiftNIOandSwiftLogto fully supportSendable, meanwhile the design ofLambdaContextshould be adapted forSendable.WIP: Fix
Sendablechecking to pass nightly CI.Motivation:
Add necessary
Sendableconformance according to Swift Concurrency adoption guidelines for Swift Server Libraries (swift-server/guides#70).Modifications:
LambdaSendableas a drop-inSendablereplacement that's compatible with prior Swift versions;LambdaHandlertoSendable;LambdaContextandLambda.InitializationContexttoLambdaSendable;EventLoopLambdaHandler.EventandEventLoopLambdaHandler.Outputto conform toLambdaSendable.