Alexander Arlt

user-defined “post-fix operators” vs. user-defined literal suffixes: https://github.com/ethereum/solidity/pull/12362#discussion_r953938583

> I really like using `using` to tie functions to literal suffixes. In my opinion, the following problems still need to be ironed out: > > 1. the literal suffixes...

We should definitely allow compile-time evaluation of user-defined pure functions.

I think we need to support all possible kinds of bytecode's. e.g. `ir`, `irOptimized`, `legacy` and `legacyOptimized`. Maybe also `wast`, `ewasm` and `ewasm.wast`? @axic what do you think?

@joseph-henry I was not able to use this function. I created a new key pair with the lib, and the code always returned an error. ```cpp if (keypair == NULL...

> I don't think this is a typo. Is something not working for you? We perform this check so that one doesn't accidentally write too much data into the internal...

I think I have a first simple working version. So far I only tested it with their `EchoServer` example, but it really just seem to work now! I still need...

So far I only adapted the code-paths that where related to MacOS - I saw in poco some Linux and Windows specific `#ifdefs` that I did not touch yet. That...

NOTE: You may need to adapt `Net/CMakeLists.txt` to change the paths pointing to `libzt` according to your environment. I tested this only on MacOS. Building ```bash git clone [email protected]:aarlt/poco-libzt cd...

@joseph-henry I think there is even much a cooler thing than poco. I would say doing exactly the same for `nodejs` would be a game changer. What do you think?