Function Back Deployment #1566
Merged
Function Back Deployment #1566
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If this is ready, can you mark it as not a draft? |
There are probably a few things that could use a bit of elaboration after the discussion on the forums (Alternatives Considered) but it is otherwise ready. |
…the forum pitch thread: - Make better arguments against the alternative design in which the `@available` attribute is augmented instead of introducing `@backDeploy`. - Reference "polyfill" as an existing term of art. - Add a bit more detail to the Future directions section.
|
I think I've addressed the feedback in the pitch thread now. |
Jumhyn
force-pushed
the
back-deploy-attribute
branch
from
f274e2d to
b77fb3a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.