Fix Issue 23674 - incompatible types for array comparison: string and string #14868
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.
This regression was introduced by #11212 (cc @kinke ).
When the array equality expression is lowered to a druntime hook, semantic analysis on the hook is performed with gagged error messages so that the failures inside it are not outputted, but rather a generic message is printed ("incompatible types for array equality"). However, there still are some checks done during the optimization phase which get silenced (in this case, an out of bounds access for static arrays). To avoid that, I am calling the optimization routine before trying semantic lowered hook.