[kwlug-disc] C function returns an integer -- ... revelations

[Mikalai Birukou]

I've just realized that C functions return integers. ... Only integer, 
cause ... what else can a processor return from its registries?

This is worth pondering on.

WASM functions return ... integers. Cause ya, what else can that stack 
machine return from its registries? (Sample ref.: 
https://developer.mozilla.org/en-US/docs/WebAssembly/Guides/Exported_functions 
)

Different runtimes meet in running mechanism, in a processor/machine. 
Running machine gets directly something little into registries, and then 
looks accordingly to places in memory. One runtime put something into 
memory. Another runtime reads from that memory. Message passing at its 
finest and basic.

Returned integer is either status, or a pointer to memory, etc. With 
this in mind, "C is assembly" is not untrue. Lisp, Java, JavaScript, 
Python and all other operate already in some virtual world, in some 
runtime. They return objects.

Rust is funky in that it is as low as C, yet, types you use are like 
"returning objects" places. One may be annoyed by nuances of types, but 
those nuances are how your effective runtime is setup. In high level 
(hallucinogenic?) languages these choice are done for you, opt-in, no 
opt-out.

TypeScript is zen of types in that they exist for developer, and don't 
exist for runtime.

Rust types also exist only in compilation, but they shape resulting 
assembly.

What are your vibes in this context?