Open cyw3 opened 6 years ago
So they hash code is calculated from the name and parameters?
Any idea how to do it so that the hash code can be a bit tolerable to changes?
On 11 Dec 2017, at 9:21 PM, cyw3 notifications@github.com wrote:
Suggest lizard can generate a hashcode id for every function! And for the same function, every time using lizard to scan it, its hashcode id is not change, unless its name or params are modifier.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/terryyin/lizard/issues/209, or mute the thread https://github.com/notifications/unsubscribe-auth/AAwJYhLsdlwo8rNm9kodWx5jNoYdcAW7ks5s_SxRgaJpZM4Q9YUH.
can use file's path and function's long name with detail namespace and function's params name, and the line number is not suggested.
if lizard have function's hashcode id, it can track the function based on the id between every time scanning. @terryyin
Suggest lizard can generate a hashcode id for every function! And for the same function, every time using lizard to scan it, its hashcode id is not change, unless its name or params are modifier.
@terryyin