libCat VS AECforWebAssembly

That's awesome! I'm working on something that sounds similar. https://github.com/cons-cat/libcat

I'd love to see your work if you're willing to share it here!

This runtime size bothers me a lot. So much that I've been working on a new runtime for C++ that breaks POSIX compatibility to keep binaries as small as they can be. The hello world with LTO is 330ish bytes right now, and I think that can get smaller. https://github.com/Cons-Cat/libCat

I'm working on a library that replaces both C++ and C/POSIX standard libraries (https://github.com/Cons-Cat/libCat), but even then I need to define a few std:: namespace symbols for some features. In the case of std::initializer_list, my answer is just don't use that feature, because you don't really need it.

It's worse in the standard library than it has to be. When I refactored my traits to minimize template instantiations and lean on concepts as much as possible, I measured over 30% improvement to clean build compile times. It's not possible for the standard to do this, because it would subtly change the API. For instance, you can't instantiate or take the address of a concept, but you can for a type-trait class. No reason you'd want to do that, but you can, so they can't "break" the standard library by optimizing this.

This doesn't have to be true. Over the past year I've made progress towards demonstrating how even non-freestanding C++ can be written without any C or C++ standard library headers or DLLs (with large benefits). There are a few names which the compilers require to be in the std:: namespace, though, but they're very special features like source_location and construct_at with semantics that can't be expressed otherwise.

This bit cast has no overhead in debug mode, and is a little bit more generally useful than std::bit_cast(), but cannot be constant evaluated. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/utility/implementations/bit_cast.tpp

It isn't that hard to put a predicate into a type. We have lambdas in an unevaluated context, CTAD, and templated type aliases. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/scaredy/cat/scaredy https://github.com/Cons-Cat/libCat/blob/main/src/global_includes.hpp#L70 https://github.com/Cons-Cat/libCat/blob/main/src/libraries/linux/cat/linux#L289 You do it like this.

But suppose that you have code with no standard library calls at all. Would it still make sense to choose this naming convention? This is actually possible, with a few special exceptions. GCC requires that an implementation of std::source_location has very particular class member names, GCC assigns special semantics to a few function names including std::construct_at and std::move (people seem to know it's inlined, but did you know std::move is required for move-related warnings?), and most intrusively of all, a promise_type must be snake_case. Other names can be worked around by using them into a different namespace with a different letter-case, but promise_type seems unavoidable.

I use C++ for a low-level Linux runtime. Other people are using it for operating systems like SerenityOS and Zircon/Fuschia. People also use C++ for making more compilers like GCC and LLVM.

Great! I have not yet made source maps for my programming language that compiles to WebAssembly, and I probably never will.

Up until today, my AEC-to-WebAssembly was, if somebody tried to use two structures of different types as the second and the third operand to the ?: (ternary conditional) operator, as in this example: ``` Structure First Consists Of Nothing; EndStructure

Well, I have written the first compiler for my programming language, targetting x86, in IE6-compatible JavaScript, and the second compiler, targetting WebAssembly, has been written in C++11. I think that, to choose a language to write a compiler in, you need to look at at least two things:

You can see the releases v2.5.3 and v2.5.2 of AECforWebAssembly on GitHub. They are produced with the same version of GCC, the only difference (as far as I know) is that v2.5.2 was produced directly on Debian, whereas v2.5.3 was cross-compiled from Windows to Linux using Docker.

That could be true. I host my AEC-to-WebAssembly compiler on GitHub, GitLab and SourceForge, and it's only on GitHub that it has 21 stars and 2 forks. On GitLab and SourceForge, it has zero of both.

Well, the main compiler for my programming language is targetting the JavaScript Virtual Machine by outputting WebAssembly. I think it's even better than targetting Java Virtual Machine, because, for one thing, your executables can run in any modern browser if you output WebAssembly. If you target Java Virtual Machine, the users need to actually download your app. Furthermore, there is an official assembler for WebAssembly called WebAssembly Binary Toolkit (WABT), so your compiler can output assembly and not have to deal with binary files. There is nothing equivalent to that for Java Virtual Machine.