Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it possible to selectively treat certain implicit type conversions as errors, or at least generate warnings when they happen?
Bad:
long x = 5; //warning, 5 is an int
float f = 10;// warning, 10 is an int
Good:
long x = 5L; //correct, no warning
float f = 10f; //correct, no warning
Edit: removed reference to bugs, since that isn’t the point of the question, and isn’t helpful.
If you were using Visual Studio Premium+, you may be able to create a Code Analysis ruleset to handle this during build time.
You could also write your own VS.NET extension and possible integrate with Roslyn to interrogate the code to the extent that the compiler is.