Wilson Cusack
@wilsoncusack
Here is our first attempt at codifying a guide for style, development, and testing of EVM-smart contracts at Coinbase. https://github.com/coinbase/solidity-style-guide Our goal is to build the best Solidity organization in the world and documentation like this is an important start :)
3 replies
4 recasts
56 reactions
Sabnock
@sabnock.eth
Think you should add a comment clarifying imports declared at file level which you don't address. As in is it permissible to have an unnamed import if what you're importing is at file-level or don't declare anything at file-level and import it at all?
1 reply
0 recast
2 reactions
Spencer Perkins
@spencerperkins.eth
Interesting choice avoiding interfaces. While removing them probably makes the individual contract easier to understand, they are a useful layer of abstraction for composing contracts or protocols (local maximum, but not global).
1 reply
0 recast
0 reaction
matt ↑ ᖽ
@blueish
Cool to see all the optimizations for legibility ( avoid inheritance, rarely use assembly, no interfaces ). Always important in swe but moreso when half the time I’m reading contracts on a block explorer and not in an editor w code nav/analysis, etc.
0 reply
0 recast
1 reaction
Zk
@risotto
Based
0 reply
0 recast
1 reaction
0xmht.eth
@0xmht
Bookmarked it. Will definitely give it a read
0 reply
0 recast
1 reaction
Leeward Bound
@leewardbound
fuck i fucking love standards, fuck
0 reply
0 recast
1 reaction
Myk.eth
@myk
Yay for ASCII art 🖼️ I’ve always wondered where to draw the line when it comes to assembly gas savings. 25% savings feels good. Lgtm
0 reply
0 recast
0 reaction
