Skip to content
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

Ask about prior art in API review template #38727

Merged
merged 2 commits into from
Jul 3, 2020
Merged

Conversation

danmoseley
Copy link
Member

As an example, #35088 described an analogous pattern in the Go ecosystem. While we have distinct patterns and rules for .NET API, if there's analogous prior art it may be interesting to compare approaches.

As an example, #35088 described an analogous pattern in the Go ecosystem. While we have distinct patterns and rules for .NET API, if there's analogous prior art it may be interesting to compare approaches.
@danmoseley
Copy link
Member Author

danmoseley commented Jul 2, 2020

Also, should I remove "if known" -- is it reasonable to expect that a decent API proposal requires at least a few minutes investigation of prior art? What are your thoughts?

I can also update the markdown.

cc @stephentoub

@stephentoub stephentoub merged commit ff1ea09 into master Jul 3, 2020
@stephentoub stephentoub deleted the danmosemsft-patch-1 branch July 3, 2020 15:48
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants