Igor Żuk

> re 1: "erzatz" is a perfectly good English word (borrowed from German): You're right, it's a correct English word. Nevertheless it's quite confusing, it's an exotic word that doesn't...

"Virtual file system" is a great term, it's widely used in the English-speaking software developer community. Just search for this term in Google, you'll get thousands of results about technologies...

> Make it possible to verify on Etherscan + Sourcify in one go I have an opinion on that, could be wrong, YMMV and all. It doesn't seem too important...

> Regarding the contract verification artifact - if the --resume workflow works as expected with --verify would this still be required? I think so, yes. This is a thread about...

A very small and dumb but actually convenient change would be to introduce `forge verify` as an alias to `forge verify-contract`. It's a very long name for such a basic...

I want to bump this issue, but I think that `StdConstants` should be just a Solidity file with a bunch of free constants, **not** another contract. This will simplify composition...

I agree that a library should be as flexible and non-intrusive as free constants. It will be usable in all kinds of functions, including library functions and free functions, and...

I believe that you're referring to this change: https://github.com/foundry-rs/forge-std/commit/14325182bf0aae5b2b858f5f0351ffe35c643248#diff-d79529fa796b868bdba7d0be181244b6d3ee5d3ff0aecb1b5db2d47b78dfb05dL15-L17 and specifically this part of `StdAssertion.sol`: ```diff - function fail(string memory err) internal virtual { - emit log_named_string("Error", err); - fail();...

Now that I'm thinking about it, my use case could be solved by just passing the extra resource paths to `pandoc.mediabag.fetch` and `.fill`. It would only affect the specific call,...

I'm not sure, but it could mean that for the readers and parsers the dynamic resource path may be already resolved. I don't understand and can't find on the internet...