this one goes out to all the haters who said "you will never figure out the rust debugger and fix sourcemaps in foundry's solidity debugger"

building /nook – farcaster & more. prev: protocol @ opensea, co-author seaport & stuff. professional @slokh and @0xalexander fanboy

sneaking suspicion i know the root cause of a third bug (sourcemap highlighting sometimes gets jumbled up)

*dj khaled voice* another one

https://github.com/foundry-rs/foundry/pull/7059

♾

Grab life by the plunger and keep pumping till you see gold.

UwU-ing my way to a better future in /harrypotter and /unicode

At least they're specific, huh.
Well played 👌

working on /bleu and just @thetip to improve it's liquidity

ty 🙏 

should help a lot with cooking up smart contracts 👨‍🍳

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

Currently: WhatsABI

this is the builtin forge debugger! sourcemaps have been broken for cross-source (eg inherited) function calls for several months now; this is a screenshot of it correctly finding the (inherited) increment() function with my fix 🤠

available with `cast run --debug` or `forge script/test --debug`

That's beautiful. Can I run this on arbitrary bytecode/without source code?