4 ms·

> So you just use an abstract structure (like sequence, map, set, table, graph) and based on the program profile, the compiler will pick the specific implementa

• js8 3y ago
  > a sudden change in perf characteristics when one additional usage of some feature tips a heuristic over This already happens with humans, changing features will change how the product is used and thus performance characteristics changes. The question is, do you trust the compiler to do a good job? Of course you won't, till the late 90s, people didn't trust compilers to do a better job than humans in assembler. So it's important to have a good UX for this feature, where the compiler communicates what data types is it using, and gives human option to override its decisions. So that users would gain trust in this feature.
  • Kamq 3y ago
    > This already happens with humans, changing features will change how the product is used and thus performance characteristics changes. Yes, but I can usually look at the function itself for what changed, or the function it calls. I don't need to look three functions away (assuming no inheritance, which I tend to avoid).