Paul Berg

Another related use case - calling undeployed library functions. When library functions are declared as public or external, the library must be deployed separately and then linked before it can...

I keep bumping into this issue every time I make a new deployment which I need to cross-reference in another repository - I forget to bump the block number. The...

I've bumped into the same situation again and spent ~15 minutes that would have been spared had Foundry detected that the contract doesn't exist on the network. cc @grandizzy I...

ooh this is exactly what I needed! I ran the tests with `-vvv` (three verbosity flags), and I got this error: > [FAIL: call to non-contract address 0xcaFe00000000000000000000000000000000BeeF] setUp() (gas:...

Fair enough!

I think that the default behavior is for NatSpec to inherit the documentation from the parent contracts' functions automatically. From the [Solidity docs](https://docs.soliditylang.org/en/v0.8.19/natspec-format.html#inheritance-notes): > Functions without NatSpec will automatically inherit...

Can we bump the priority of https://github.com/foundry-rs/foundry/issues/4762 up to "Medium"? 1. It's a subtle cause for failing tests, which can result in long-winded debugging sessions. 2. For complex code bases...

Alternatively, a utility function to check if a single character is alphanumeric would also be helpful: ```solidity function isAlphanumericChar(bytes1 char) internal pure returns (bool) { bool isSpace = char ==...

Good point. NFT UIs should definitely be aware of the possibility of XSS attacks, but I also find it helpful to add an onchain check to minimize the potential harm.

Closing as not planned.