alpharush

@man715 bump

If you have a questions, please head over to our discussions page https://github.com/crytic/slither/discussions

What version of foundry are you using? Alos, does `slither . --compile-force-framework hardhat` **without** `--ignore compile` work?

@bart1e Is this different from what is outlined here https://github.com/crytic/slither/blob/4c976d5af56219eeef079e03a35009af3e03644d/slither/solc_parsing/expressions/find_variable.py#L420-L439

@DarkaMaul This may be a simple performance win

I can not reproduce this. Is this the exact contract that you got this error on? This is not related to false negatives since the trace has a crash

This was changed purposely in https://github.com/crytic/slither/pull/2370. It used to be a late lookup and caused issues with aliasing. In retrospect, I probably could have replaced uses of `contract_name` where I...

Ah I see. I didn't update the signature of slither.core.expressions.new_contract.NewContract https://github.com/crytic/slither/pull/2370/files#diff-fd01d1c9135cdceee138701706ce2947d135c9b32bf89253c5ca2f84a54979d9R619

~@kevinclancy This is related to the argument reordering~ EDIT: It might actually be related to https://github.com/crytic/slither/issues/1622

Can you provide more information on reproducing this? It is invariant that a detector is found if we are creating result output