News for hackers. Stuff that matters.
Re:C++ Core Coroutines Proposal [pdf] by pcwalton on Friday September 21, 2018 @07:51AM (#18038986)
It's because defining "customization points" as operators make it easier to write templates, essentially. See "C++ doesn’t know how to do customization points that aren’t operators": https://quuxplusone.github.io/blog/2018/08/23/customization-...

This is one of the downsides of not having typeclasses that is often forgotten about.

Re:C++ Core Coroutines Proposal [pdf] by aaaaaaaaaab on Friday September 21, 2018 @01:22PM (#18041201)
Wouldn’t uniform call syntax (like in D) solve most of the issues outlined above? I.e. it always boils down to “primitive types can’t have methods”; but uniform call syntax would let us call any function like a method on its first argument...
Re:C++ Core Coroutines Proposal [pdf] by pcwalton on Friday September 21, 2018 @01:47PM (#18041386)
Or just allow methods to be defined on primitive types, like Rust.
Re:C++ Core Coroutines Proposal [pdf] by aaaaaaaaaab on Friday September 21, 2018 @01:58PM (#18041468)
Uniform call syntax is a superset of that, since you can’t have virtual methods on primitive types.
Re:C++ Core Coroutines Proposal [pdf] by cheez on Friday September 21, 2018 @12:15PM (#18040732)
That's why I cannot wait for concepts