* improve windows builds
* install nasm for openssl compilation on win
* install nasm for openssl compilation on win for github
* add create-state, proxy-liteserver, rldp-http-proxy, http-proxy, adnl-proxy, dht-server, libtonlibjson.so and libemulator.so to docker image
* build new artifacts inside Docker
* add files smartcont/auto/* to docker image
* build arm64 in docker branch build
* improve secp256k1 build
* adding natively portable binaries (all statically linked with libc++, without nixpkgs help) for x86-64 linux
* install missing headers on ubuntu 20.04
* use clang-16 on ubuntu 20.04
* remove gsl for portable artifacts; add -f key to generate-random-id in order to read addr_list from file;
* typo
* decode json
* decode json
* add github workflow for appimages creation
* add missing dependencies
* use libc++ for appimages artifacts
* typo
* appimages wihtout libc++
* appimages with libc++ and some checks
* add appimages to release (for testing)
* add appimages to release (for testing)
* add appimages to release (for testing)
* add appimages to release (for testing) 2
* add appimages to release (for testing) 3
* appimages only on ubuntu 22 with ssl-3 for now
* appimages only on ubuntu 20 with ssl-3 for now
* appimages only on ubuntu 20 with ssl-3 for now
* add export LD_LIBRARY_PATH="${APPDIR}/usr/lib:${LD_LIBRARY_PATH}" to appimage AppRun
* create release
* appimages without jemalloc
* bind specific libraries to appimages
* add libreadline
* add plain portable libs
* add proper /lib/x86_64-linux-gnu/libreadline.so.8
* app images build with libc
* try to ensure ABI compatibility with older glibc
* try to ensure ABI compatibility with older glibc for shared libraries
* shared lib without libc but with D_GLIBCXX_USE_CXX11_ABI and -static-libgcc -static-libstdc++
* add -fPIC -fcommon
* add /lib/x86_64-linux-gnu/libstdc++.so.6 to static binaries
* add -static-libgcc -static-libstdc++ to libtonlibjson and emulator when PORTABLE=1
* add -static-libgcc -static-libstdc++ to libtonlibjson and emulator when PORTABLE=1
* update emulator portable
* Update CMakeLists.txt
* test portable macos binaries
* do not use -static-libgcc -static-libstdc++ on mac for shared libs
* do not use -static-libgcc -static-libstdc++ on mac for shared libs
* adjust create-release.yml
* minor fixes, typos
* minor fixes
* linux apps double check
* avoid infinite loop when place in system bin dir
* avoid infinite loop when place in system bin dir 2
* test compilation on linux arm64
* test appimages on arm64 linux
* test appimages on arm64 linux 2
* add portable linux arm64 to release
* clean up
* update README.md
* improve windows builds
* install nasm for openssl compilation on win
* install nasm for openssl compilation on win for github
* add create-state, proxy-liteserver, rldp-http-proxy, http-proxy, adnl-proxy, dht-server, libtonlibjson.so and libemulator.so to docker image
* build new artifacts inside Docker
* add files smartcont/auto/* to docker image
* build arm64 in docker branch build
* improve secp256k1 build
* extend generate-random-id with -f parameter (to read addr list from a file)
* Accelerator: partial fullnodes
1) Node can monitor a subset of shards
2) New archive slice format (sharded)
3) Validators are still required to have all shards
4) Support partial liteservers in lite-client, blockchain explorer, tonlib
5) Proxy liteserver
* Fix compilation error
Unary logical NOT was already implemented earlier.
Logical AND OR are expressed via conditional expression:
* a && b -> a ? (b != 0) : 0
* a || b -> a ? 1 : (b != 0)
They work as expected in any expressions. For instance, having
`cond && f()`, f is called only if cond is true.
For primitive cases, like `a > 0 && b > 0`, Fift code is not optimal,
it could potentially be without IFs.
These are moments of future optimizations. For now, it's more than enough.
Instead on 'ton_crypto', Tolk now depends on 'ton_crypto_core'.
The only purpose of ton_crypto (in FunC also, btw) is address parsing:
"EQCRDM9...", "0:52b3..." and so on.
Such parsing has been implemented manually exactly the same way.
This is a very big change.
If FunC has `.methods()` and `~methods()`, Tolk has only dot,
one and only way to call a `.method()`.
A method may mutate an object, or may not.
It's a behavioral and semantic difference from FunC.
- `cs.loadInt(32)` modifies a slice and returns an integer
- `b.storeInt(x, 32)` modifies a builder
- `b = b.storeInt()` also works, since it not only modifies, but returns
- chained methods also work, they return `self`
- everything works exactly as expected, similar to JS
- no runtime overhead, exactly same Fift instructions
- custom methods are created with ease
- tilda `~` does not exist in Tolk at all
