Unverified Commit 74a106f1 authored by 82marbag's avatar 82marbag Committed by GitHub
Browse files

Update Status of RFCs (#1593) 



* Update Status of RFCs

Signed-off-by: default avatarDaniele Ahmed <ahmeddan@amazon.de>
parent 3d53e740

design/src/rfcs/rfc0015_using_features_responsibly.md

+1 −1
Original line number Diff line number Diff line 
# RFC: How Cargo "features" should be used in the SDK and runtime crates



> Status: RFC

> Status: Accepted



## Some background on features

design/src/rfcs/rfc0016_flexible_checksum_support.md

+1 −1
Original line number Diff line number Diff line 
RFC: Supporting Flexible Checksums

==================================



> Status: RFC

> Status: Implemented



We can't currently update the S3 SDK because we don't support the new "Flexible Checksums" feature. This RFC describes this new feature and details how we should implement it in `smithy-rs`.

design/src/rfcs/rfc0018_logging_sensitive.md

+1 −1
Original line number Diff line number Diff line 
# RFC: Logging in the Presence of Sensitive Data



> Status: RFC

> Status: Accepted



Smithy provides a [sensitive trait](https://awslabs.github.io/smithy/1.0/spec/core/documentation-traits.html#sensitive-trait) which exists as a `@sensitive` field annotation syntactically and has the following semantics:

design/src/rfcs/rfc0019_event_streams_errors.md

+1 −1
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ RFC: Errors for event streams 
=============



<!-- RFCs start with the "RFC" status and are then either "Implemented" or "Rejected".  -->

> Status: RFC

> Status: Implemented



<!-- A great RFC will include a list of changes at the bottom so that the implementor can be sure they haven't missed anything -->

For a summarized list of proposed changes, see the [Changes Checklist](#changes-checklist) section.