Sure, but the more structure your video has to have, the harder it becomes to hide information stenographically within it. Your information density will become very low I think.
I completely disagree. Putting builtins on some special pedestal and demoting user-defined classes and functions is always a mistake IMO. I also don't see how this is a reasonable approach even in the cases you mention. If map is polymorphic, but I can't define polymorphic classes myself, it seems impossible to define classes that can hold arbitrary maps. So I can't even wrap map.
Also, if I'm reading https://go.dev/tour/moretypes/15 correctly, append is a variadic function and not a polymorphic function. That's something very different.
> Also, if I'm reading https://go.dev/tour/moretypes/15 correctly, append is a variadic function and not a polymorphic function. That's something very different.
It is both variadic and polymorphic.
> Putting builtins on some special pedestal and demoting user-defined classes and functions is always a mistake IMO.
There is a line of thought in programming language design that claims everything should be user defined, but too much customization of everything inevitably leads to a lot of fragmentation, subtle incompatibilities and lots of ways to solve the same simple problem.
Avoiding all of these issues is an important part of go's reasoning behind some of their design choices and the proposed idea could probably fit that quite well.
You're talking about backed stablecoins which are only a subset of stablecoins. In the common usage of the term, stablecoins include both backed stablecoins and algorithmic stablecoins.
