Ethereum

Compilation errors due to change in Azure library "github.com/Azure/azure-storage-blob-go/azblob"

In /build/ci.go : func doPurge()

Line 1241: blobs[i].Name undefined (type invalid type has no field or method Name)

In /internal/build/azure.go

line 73: BlobItem not declared by package

And others ....

Apparently we have the assert macro disabled in CI, even in non-release builds - at least on Windows (see ethereum/solidity#12634 (comment)). While this macro is generally discouraged in our project in favor of the solAssert() family of macros, we still do have them in some places and I think that they should

Issue

Vyper handles unmapped instructions differently from Solidity. In Solidity, unmapped instructions are given a file index of -1. When attempting to show the source for such an instruction, we instead just show 1: // No source code found..

However, in Vyper, such instructions are not given a file index of -1, but are given a start and length of 0. So when we show the source for t

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for