Do some code cleaning

Author: stevapple

Examples/LambdaFunctions/README.md

@@ -27,7 +27,7 @@ Steps to deploy this sample to AWS Lambda using the AWS CLI:
   ./scripts/deploy.sh
   ```
 
-  Notes: 
+  Notes:
   - This script assumes you have AWS CLI installed and credentials setup in `~/.aws/credentials`.
   - The default lambda function name is `SwiftSample`. You can specify a different one updating `lambda_name` in `deploy.sh`
   - Update `s3_bucket=swift-lambda-test` in `deploy.sh` before running (AWS S3 buckets require a unique global name)
@@ -87,7 +87,7 @@ The SAM template will provide an output labelled `LambdaApiGatewayEndpoint` whic
 
   ```
   curl <<LambdaApiGatewayEndpoint>>
-  ```  
+  ```
 
 ***Warning:*** This SAM template is only intended as a sample and creates a publicly accessible HTTP endpoint.
 
@@ -129,7 +129,7 @@ The `serverless-deploy.sh` script passes through any parameters to the Serverles
 
 For the APIGateway sample:
 
-The Serverless template will provide an endpoint which you can use to test the Lambda. 
+The Serverless template will provide an endpoint which you can use to test the Lambda.
 
 Outuput example:
 
@@ -162,7 +162,7 @@ For example:
 
   ```
   curl https://r39lvhfng3.execute-api.us-east-1.amazonaws.com/api
-  ```  
+  ```
 
 ***Warning:*** This Serverless template is only intended as a sample and creates a publicly accessible HTTP endpoint.
 

Examples/LambdaFunctions/scripts/SAM/ErrorHandling-template.yml

@@ -10,5 +10,5 @@ Resources:
       Handler: Provided
       Runtime: provided
       CodeUri: ../../.build/lambda/ErrorHandling/lambda.zip
-# Instructs new versions to be published to an alias named "live".      
+# Instructs new versions to be published to an alias named "live".
       AutoPublishAlias: live

Examples/LambdaFunctions/scripts/serverless/APIGateway-template.yml

@@ -16,7 +16,7 @@ provider:
               - logs:CreateLogGroup
               - logs:CreateLogStream
               - logs:PutLogEvents
-          Resource: "*"        
+          Resource: "*"
 
 functions:
     httpGet:

Examples/LambdaFunctions/scripts/serverless/Benchmark-template.yml

@@ -12,7 +12,7 @@ provider:
               - logs:CreateLogGroup
               - logs:CreateLogStream
               - logs:PutLogEvents
-          Resource: "*"        
+          Resource: "*"
 
 functions:
     benchmarkFunction:

Examples/LambdaFunctions/scripts/serverless/CurrencyExchange-template.yml

@@ -12,7 +12,7 @@ provider:
               - logs:CreateLogGroup
               - logs:CreateLogStream
               - logs:PutLogEvents
-          Resource: "*"        
+          Resource: "*"
 
 functions:
     currencyExchangeFunction:

Examples/LambdaFunctions/scripts/serverless/ErrorHandling-template.yml

@@ -12,7 +12,7 @@ provider:
               - logs:CreateLogGroup
               - logs:CreateLogStream
               - logs:PutLogEvents
-          Resource: "*"        
+          Resource: "*"
 
 functions:
     errorHandlingFunction:

Examples/LambdaFunctions/scripts/serverless/HelloWorld-template.yml

@@ -12,7 +12,7 @@ provider:
               - logs:CreateLogGroup
               - logs:CreateLogStream
               - logs:PutLogEvents
-          Resource: "*"        
+          Resource: "*"
 
 functions:
     hello:

Sources/AWSLambdaRuntimeCore/Utils.swift

@@ -13,7 +13,6 @@
 //===----------------------------------------------------------------------===//
 
 import Dispatch
-import NIOPosix
 
 internal enum Consts {
     static let apiPrefix = "/2018-06-01"

Sources/AWSLambdaTesting/Lambda+Testing.swift

@@ -37,7 +37,6 @@
 
 #if compiler(>=5.5) && canImport(_Concurrency)
 import AWSLambdaRuntime
-import AWSLambdaRuntimeCore
 import Dispatch
 import Logging
 import NIOCore

readme.md

@@ -144,7 +144,7 @@ First, add a dependency on the event packages:
 
  Beyond the small cognitive complexity of using the `EventLoopFuture` based APIs, note these APIs should be used with extra care. An `EventLoopLambdaHandler` will execute the user code on the same `EventLoop` (thread) as the library, making processing faster but requiring the user code to never call blocking APIs as it might prevent the underlying process from functioning.
 
-## Deploying to AWS Lambda   
+## Deploying to AWS Lambda
 
 To deploy Lambda functions to AWS Lambda, you need to compile the code for Amazon Linux which is the OS used on AWS Lambda microVMs, package it as a Zip file, and upload to AWS.
 
@@ -160,7 +160,7 @@ The library defines three protocols for the implementation of a Lambda Handler.
 
 ### ByteBufferLambdaHandler
 
-An `EventLoopFuture` based processing protocol for a Lambda that takes a `ByteBuffer` and returns a `ByteBuffer?` asynchronously.  
+An `EventLoopFuture` based processing protocol for a Lambda that takes a `ByteBuffer` and returns a `ByteBuffer?` asynchronously.
 
 `ByteBufferLambdaHandler` is the lowest level protocol designed to power the higher level `EventLoopLambdaHandler` and `LambdaHandler` based APIs. Users are not expected to use this protocol, though some performance sensitive applications that operate at the `ByteBuffer` level or have special serialization needs may choose to do so.