The Solidity Contract-Oriented Programming Language - By chatting here you agree to the https://github.com/ethereum/solidity/blob/develop/CODE_OF_CONDUCT.md
uint[1000] memory bla; test(bla); with function test(uint[1000] memory a) internal { a[0] = ...; }?
function another() external returns(bytes memory){
bytes memory k = hex"94C3";
return k;
}94C3 appears two times
--via-ir would already decrease some unnecessary memory allocations when compared to the current codegen. If you absolutely want cheaper code, this might be a solution for now.
And the duplicate
94C3 comes from the fact that memory is always allocated for the return variable, even if the compiler could just reuse the variable that is being returned.
Hi, we (my brother and me) build a algorithmic hedging protocol. The goal of hedgehog is to allow fully decentralized chain hedging against depreciation of on chain assets. Please look at the site for more information. We are curious about your opinion and if you would like to promote this towards your community? Please let me know and if you have further questions please let us know!
Kind regards,
Mitchell & Kevin Foesenek
bytes type value and actually Remix doesnt compile if I use the exact same structure but it does if I replace bytes by bytes32, I was wondering if it will be interpreted the same way by the external contract ? My contract needs to be compiled with 0.7.6 and the target contract was compiled with 0.5.12. Maybe it can help to answer: If I disable optimization, the contract compile but with the Contract code size exceeds 24576 bytes message. I dont understand how optimization and bytes type are linked and why Remix isnt throwing me any error when the compilation fails, he just doesnt compile with bytes type in a struct (any struct, even in a called library..).
Actually it concerns a large code base, it works if I try something like this :
pragma solidity ^0.7.6;
pragma experimental ABIEncoderV2;//SPDX-License-Identifier: UNLICENSED
contract FailCompilation {
struct Test {
bytes Value;
}
}
but thats exactly the issue. In my contract, if I add any struct that contains a bytes value, Remix compiler wont compile and doesnt throw any error, but it works if I use bytes32 instead of bytes. Only if I enable optimization, without optimization I just have the Contract code size exceeds 24576 bytes warning from Remix but the compilation is done.
Remix compiler wont compile and doesnt throw any error
This is weird.
Could you try to compile it locally with solc? That would remove some layers in between and might make the problem easier to diagnose.
solc would give you at least the location of the crash in the source, even if there's no message attached.
bytes32 instead of bytes is successfully compiling with solc and optimization enabled
4 replies
This is an ongoing issue that we're trying to solve with the optimizer but there are only 16 stack slots reachable at any given time so it's not that easy.
But I still don't understand the schema in grammar docs ^
Hi everyone..
I have the following:
static combinedHash(first: Buffer, second: Buffer): Buffer {
if (!first) {
return second
}
if (!second) {
return first
}
return keccak256(MerkleTree.sortAndConcat(first, second))
}keccak256 is imported from ethereumjs-utils
It seems like that keccak256 returns Buffer . I don't know why.
What I am trying to do is I want to change keccak256 from ethereumjs-utils to ethers/lib/utils, but new keccak256 doesn't return buffer. I tried lots of things, but the results are different. any ideas ?