"Even high-spec machines can run out of memory while compiling parts of the Solana codebase."

🤣

Building Solidity's compiler solc is nothing short of a bear. It is using complex external dependencies like boost with some optional dependencies. Moreover the build depends on specific versions of these packages. This amount of complexity for a compiler is a topic of another post but it does give me …

This simple solidity example is super useful for testing transaction processing. It globally sets a value by address which will default to sender but may also be specified.

Solidity AddressStore - Save a value globally on chain

Solidity modifiers are evaluated from left to right. It makes sense to order modifiers in order of those that are most likely to fail to those that are least likely to fail. It is also a good idea to order them from most primitive to most expensive. And prerequisite conditions …

If you want to apply a script to each file in a folder recursively you may not want the full relative path. Here is how to remove it.

$ find . -type f -print | sed -e "s|^\./||g"

For example to combine it with xargs and invoke a script on each name …

I was able to get solidity docgen working by implementing a series of three different stages all automated in our build process.

1. Parse the solc output into actual json.
2. Load the json file into the documentation system
3. Use a Jinja template to convert the api document

There is shockingly poor …