hrkrshnn

If it's more about improving the compiler, you can ask on gitter.im/ethereum/solidity-dev

You can generally ask on gitter.im/ethereum/solidity

I'm @hrkrshnn on gitter. And @hrkrshnn:matrix.org on matrix

How about matrix?

Yeah. This has to be done by the optimizer.

Yeah. That sounds right.

In this example, r would return 0.

```
contract C {
    function f() public returns(uint r) {
        assembly {
            r := mload(10000)
        }
    }
}

contract D {
    C c = new C();

    function g() public returns(uint old, uint intme, uint aft, uint Cmemory) {
        assembly {
            old := mload(10000)
            mstore(10000, 200)
            intme := mload(10000)
        }

        Cmemory = c.f();

        assembly {
            aft := mload(10000)
        }
    }
}
```

For one, it's not in the memory after you do the external call.

How else would you do it?

You need to store it before you do the external call.

Yeah.

That is, to remove the unnecessary copy.

Yes. This is the job of the optimizer. It currently can't handle this case.

In your example, you don't need a copy.

But the abi encoding can be different. Which is why you need a copy.

Yep

@NikaKurashvili tagging just in case, you don't get notified otherwise.

and gitter.im/ethereum/solidity-dev?at=6017cfb04f7d1b68e522e3a9

gitter.im/ethereum/solidity-dev?at=6013f97b4f7d1b68e519419c relevant.

In this case, the encoding is the same, though.

Hi again. So the problem is that, in general the copy memory -> memory is the abi encoding of the memory object. In general, it may not be the same.

Yeah. Not sure about this. I've to look more into the reasons.

There seems to be an extra copy.

Interesting. I was taking a quick look at the intermediate representation.

Is that difference with the optimizer enabled?

If you use memory then there would be the copies: calldata -> memory -> call-opcode. The same remains even when you use calldata.

No. If you look here, call opcode needs its input from memory. So calldata -> memory is a must.

Because it's an external call. Actually my older comment was incorrect. There would be a copy even when both the arguments are in calldata. Because the call opcode needs its input in memory. So I think using memory or calldata in your test function probably doesn't make any difference, gas wise. However, changing to calldata in again should be cheaper.

You can replace uint[3] memory bla and uint[3] memory haha to uint[3] calldata .... The compiler copies it since you wrote that the array is in memory.

@AaronHall Not sure if this is what you are looking for, but you could use latex_header to achieve things like changing themes, remove or add footers, etc.

Now, I've to leave. Talk to you soon.

gitk or git-gui in the repo.

Okay! Try gitk and you can find my email there.

Anyway, I'll be stuck in the airport for about 6hrs this Friday. I can make use of the time trying to fix the issues if you can provide me with access to the server.

Can you paste the output of tags/tags somewhere?

So what are the current issues that you are facing?

I will have some spare time this friday and saturday. Hopefully, I can work on it.

@RobertCardona Does make tags populate the tags/tags file?

This is a paste of the output.

I'm getting errors executing make tags.

@Robert Can you upload code for the site?

That's unfortunate.

Is there some way to circumvent the minimum rep (like mod-intervention)?

The subreddit currently has 99 readers!

I still don't quite understand the tags, though.

Even I was thinking the same.

How will the webpage be organized? Is each section going to correspond to an exercise?

That's cool.

@RobertCardona So have you tried setting up the server? Is there something that I can help?