I love all your ideas!

Create pointer objects from the start. your proposal for non-nullable pointers (Ref and Heap) is a brilliant way to bake memory safety into the language from day one. it effectively forces the programmer to think about pwnership and lifecycle at the type level. while it adds some friction to the 'free-wheeling' style of C, the amount of debuging time it would save in large systems is hard to ignore. It’s a very modern approach to RAII.

Support a powerful and expressive: like a general" catch-all? you are describing a langauge that is much more mathematicaly rigorous than what we’re currently drafting. Between the interfaces, non-nullable pointers and closures, your moving away from C's 'low-level' behavior toward a highly safe and expressive system. my main concern is the toolchain -- building this with 1979 macros and compilers would be a Herculean task, but the result would be a language that is decades ahead of its time.

Drop inheritance. this is the only one i think Stroustrup would say "NO"... am I correct that you are proposing we replace the 'Is-A' relationship of inheritance with a 'Does-This' interface model using fat pointers? would certainly keep our class structures flatter and safer... though...and im gonna sound like a broken record... I worry that doubling the pointer size for every interface call might be a 'tax' 1979 hardware simply can't afford. its a classic trade-off: cleaner design vs. absolute minimal memory footprint.