I feel that a warning indicates that there are issues with your project that need to be resolved, but you responded by saying that these warnings can be ignored
Can I completely ignore all warnings? And it won’t cause any problems?
If possible, can the project file be configured to ignore all warnings? Thank you
Warnings are called warnings and not errors for a reason. They don’t prevent compilation from completing successfully. They tell you about potential issues in your code. Potential is an important word in that sentence. Sometimes, you actually want to do the thing that the compiler is warning you not to do. In that case, you often don’t have a choice but to accept that a warning will be reported.
In the code that you write, I encourage you to try to fix all warnings reported by the compiler. They may indicate some kind of issue that isn’t critical enough to be considered an error, but may have unexpected bad side effects in certain situations.
In code written by someone else, it’s probably best to assume that the author determined that a particular warning is not a serious concern. Or it may be something that needs to be addressed in the future, but it isn’t a priority to fix it today. Of course, if you encounter a warning in someone else’s code, you are welcome to report a bug to the project, if you think that a warning is valid and should be addressed.
When I talk about ignoring warnings, I’m mainly referring to code written by someone else. Writing your own code is probably more important than spending time worrying about a warning in someone else’s code.
The Haxe compiler provides some options to disable warnings. Some appear to be relatively new in Haxe 4.3.
I would never disable all warnings in my projects. Warnings can be helpful, even if you need to ignore some of them.