extcodesize check.
Hello everybody, I am very new in Solidity and also in JavaScript. I finished the CryptoZombies tutorial (maybe you know that) and now I am just playing around a bit to display some things via Javascript.
I have the following problem: I have an array where some parameters as "name" "age" etc are stored and a mapping where it is stored which array entry belongs to which user. So there are more than one entry per address possible.
My problem now is, if I want to display it and I use a "while"-pattern, the while pattern is finished before the results from the smart contract querys are there. And also the results from the smart contract array are not always available in the order requested. so an example:
according to the mapping array entry 0, 3 and 4 belong to some specific address.
so i implemented a while pattern and requested entrys 0, 3 and 4 of the array in the contract but results got in order 3, 0, 4. From MySQL and PHP what I learned several years ago the results are always presented in the order you wanted them. Any suggestions?
1 reply
Just updates README and changes branches and repo URLs.
The only situations I can think of that it would affect are rare corner cases like this one where we rely on the size of the binary.
And we can restore that and add the switch if we run into something were we do want the metadata.
CMAKE_BUILD_TYPE=, the solc binary has 400 MB...
1 reply
Because the next test (expected behavior) passes, and the test after that (same expected behavior) fails
pragma solidity >= 0.0.0;
contract C0 {
modifier m0(uint i1)
{
_;
}
function IRReturnsZero() external m0(o0++) m0(o0++) returns (uint o0, uint o1)
{
}
}
// ====
// compileViaYul: true
// ----
// IRReturnsZero() -> 0, 0pragma solidity >= 0.0.0;
contract C0 {
modifier m0(uint i1)
{
_;
}
function IRReturnsTwo() external m0(o0++) m0(o0++) returns (uint o0)
{
}
}
// ====
// compileViaYul: true
// ----
// IRReturnsTwo() -> 0The latter test returns 2 instead of 0 and that's the bug
1 reply
1 reply
Here's another example where some garbage value is being returned (instead of zero address)
contract C0 {
modifier m0()
{
_;
}
struct St0 {
bool el0;
string el1;
address el2;
}
type T0 is bool;
function f0() external m0 returns(C0.St0 memory o0,C0.T0 o1)
{
return (o0, C0.T0.wrap(true));
}
function g() external returns (address)
{
(C0.St0 memory r1, C0.T0 r2) = this.f0();
return r1.el2;
}
}
// ====
// compileViaYul: true
// ----
// f0() -> 64, true, 0x00, 0x60, 0, ""
// g() -> 0g() should return 0 but it returns 0xe0
1 reply
function fun_IRReturnsZero_23_inner(_13, _14) -> var_o0_18, var_o1_20 {
var_o1_20 := _13
var_o1_20 := _14
}_18 instead of _20
keccak nowadays, especially keccak running out of gas. What changed in the fuzzer?
1 reply
It should also be noted that SELFDESTRUCT (0xff) has no immediate effect on nonce or code, thus a contract cannot be destroyed and recreated within one transaction.
From https://eips.ethereum.org/EIPS/eip-1014. What does that mean?
contract C {
function f() external {
selfdestruct(payable(msg.sender));
}
function g() external returns (bool) {
return true;
}
}
contract Test {
C c = new C{salt: bytes32("test")}();
function test() external returns (bool) {
c.f();
c = new C{salt: bytes32("test")}();
c.g();
return true;
}
}
// ====
// compileViaYul: also
// ----
// test() -> truekeccak does not have any side effects (assuming no msize), so you can evaluate it at any point in that sense, except for gas considerations.
contract C0 {
function f1() external returns (bytes memory o0)
{
assembly
{
{
for { o0 := selfbalance() } o0
{
o0 := keccak256(0, 1155939646350332)
} {}
}
}
}
}let tmp = keccak(...) for { o0 := selfbalance() } o0 { o0 := tmp} {} happening
1 reply