You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
At 2018-09-26T05:03:18Z, mmaxfield@apple.com wrote:
The dynamic creation of operator==() in Checker causes later checks to succeed or fail. For example, if you cause Checker to generate native bool operator==(int* thread,int* thread) and native bool operator==(int* thread* thread,int* thread* thread), later calls with (nullptr, nullptr) will fail because of an ambiguous overload.
The text was updated successfully, but these errors were encountered:
Migrated from https://bugs.webkit.org/show_bug.cgi?id=189988:
At 2018-09-26T05:03:18Z, mmaxfield@apple.com wrote:
The dynamic creation of operator==() in Checker causes later checks to succeed or fail. For example, if you cause Checker to generate native bool operator==(int* thread,int* thread) and native bool operator==(int* thread* thread,int* thread* thread), later calls with (nullptr, nullptr) will fail because of an ambiguous overload.
The text was updated successfully, but these errors were encountered: