HI std-proposals WG21,

The bekow message didn’t go through due to me using @isocpp.org instead of @lists.isocpp.org in the address. Since then, been busy surviving (for a while literally - since 12.3.2026, now having the first proped medic report since y’day - but also related to negotiations which might or might not require me to remove EPAM - or a local office of it - from the discussion, so *consider that* before replying - not representing or represented by a group of a multi-billionaree valuation, when, 2 days after the recent changes in Hungary some ‘surely not’ police agents asked for my phone to make a call and then started to search my money, joined the search :J).

The dramatic context is, and me being aware fully, when we write such a proposal, standardisation or similar, each and every aspect of it is verified, reflected back and tested on - and, in this case, since it’s apparent that it’s not only used for coding, but also reasoning in C++, to express thoughts and ideas in regions of our world that are better verified before communicated; where problems are only or mostly/preferably brought to light with proposed solution, like in genetics where we discuss up to human(!) birth, sociometry where we consider the structure of the society (including in some territories gender and religious belief/explanatory research, of which some are banned in some specific countries and we must use alternatives or parallels in terms of location or wording), physics modeling and ABI comprehensiveness limits (whether we are quantum-ready or even above that), code security (where we took a hit from Rust & it’s acceptance in govt sector) et. al. - so it’s tested on actual persons. In this case, we went back to sending messqges via VHF and actual agents, simulated some banking perspectives, can’t say haven’t patented some (so that sufficient control is established and we won’t run into that many kinds of troubles later with ill-formed first-a-good ideas of applicatkon). Literally tested, to some extent, on sea, ground and air and when discussing with that little snake of a language but not falling for it :), rather checking how it can be used with WASM and completely distributed ABIs, wrote a Musical and a cartoon of it (technically speaking - when in Hungary - it’s an «AI test log», the AI being prepared mostly in Luxembourg in an office rented for the purpose, on French servers and discussed in the Netherlands - and being discussed with Swiss/UN side besides some local defense / defense consultant side discussions and checks). The list is preliminary.

That said, *officially speaking*, so that there’s inclusion from territories where legislation does not yet permit e.g. gender research examples, or countries where even reasoning about CRISPR/Cas9, SCNT and iPSC and how these historically evolved while we were constantly discussing the standard; or how it affects (or what it reflects from) banks not only via bond-equity hedge, but e.g. oil sector and global macro (and for the jokes on «coding» and «status 1» in C++ vs. medic IT, have a suitcase for my medic reports), so *officially speaking* these are «AI-generated test logs» of or for a standard proposal and an implementation that’s already there to test in a however hacky way. This is actually created that way, after immerse amount of AI hacking and fine-tuning with equipment and toolings you don’t expect to see around yourself everyday, with more architectures on a table sometimes than in a museum - and with a little capy bearing the weight of an e-book reader on a machine :J which I used as a child, when learned assembly before C++ took the hard work off the shoulders in some contexts, similarly to when we can use it for embedded (FPGA HLS) and, after this proposal, a bit more on the market / area of VLSI, for directed hypergraphs pf evaluation can express routings better (and, in this context, from telco we have experience, whether University or Communities/Boards)..

In short, we suggest picking up from where coroutines didn’t fully deliver (or could’ve delivered more, had we had statement expressions proposal included).

We suggest standardising monadic c++ and unevaluated contexts (that bring operator overoads, as it’s described / will have been described, depending on your access, in the CppMusical). These are as simple as a marker cpass<> for monadics and uneval<> for unevaluated and are «purely sytax changes», as many changes are explainable as such in c++’s order and progress; but it helps making the code cleaner and provides further error handling and safe(r) codes.

Furthermore, it’s only «AI-generated» until we find (or until legislation permits) the proper people to rewrite parts, eventually rewriting possibly the entire proposal - in fact, for that, not having some big name on it might actually help; but, if you need to have ‘a name’ on it, the related patenting in a particular sector is dedicated to M. Szollosi and testing systems based on this to keep track of what was promised to him the last time we talked (and that’s not a previous, but an actual ‘last’, in this world).

Examples available on github currently (considering duplicanting the effort on the Dutch equivalent for legislational diversity); codes and docs linked below.

Cheers,

lorro (Lorand SZOLLOSI / Lorand J SZOLLOSI)

Begin forwarded message: