r0qs
r0qs
Thank you very much. Yeah, I just started to do my own implementation of it here, but I'll definitely keep a eye on the next releases.
Hey this is great news! And I like the originally proposed names (without the `-js`). About the `feeds` repo, I believe that the existent one pointed by @agazso looks more...
Hi @xx014939, can you provide more details of your setup? What version of solc-js are you using? Probably related to https://github.com/ethereum/solc-js/issues/627
Hi @xx014939, in which browser are you testing? Chromium-based browsers seem to have a problem loading the wasm binary in the main thread. So you are currently required to use...
> * Rename `New Issues` column on the [old board](https://github.com/ethereum/solidity/projects/43) to `Triage` and start adding new issues there for now until we figure out if we can do it for...
Closing in favor of https://github.com/ethereum/solidity/issues/13615
Yes, it is a slice of TXOutput: https://github.com/Jeiwan/blockchain_go/blob/master/transaction_output.go#L36
> @r0qs I see there's a merge commit. Can you rebase it on top of `master` instead? Yes. I did it now, but as the commits were very old and...
> ~Yes, or even use `must have` or `must have eventually` with prevent the bot to mark it as stale.~ Just a small correction since `must have` is only used...
> One more thing. Maybe you could also create a separate `nightly-ossfuzz` workflow and move `t_ubu_ossfuzz` to it? This way we could re-enable failure notifications for the other nightly jobs....