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

Review What "deprecate" Metadata Can Meaningfully be Applied To #2130

Open
InsertCreativityHere opened this issue May 7, 2024 · 0 comments
Assignees
Milestone

Comments

@InsertCreativityHere
Copy link
Member

Due to our non-existent metadata validation, the Slice compiler allows you to put ["deprecate"] on pretty much anything.
But, what this actually affects is very language dependent, and I think we should make it more consistent,
preferably by handling it more gracefully in more languages.

For example, in C++, ["deprecate"] only has an effect on operations and interfaces.
But I don't see a reason not to handle this for structs, exceptions, etc as well. We could generate [[deprecated]] on them all the same.

Whereas in C# and Java, we correctly handle this for all kinds of stuff, operations, enums, structs, everything you'd expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants