Andrei Alexandrescu

Added statically-typed versions of all functions, so if people write `typeid(T).func` in generic code, an efficient version is picked up.

Per discussions with @WalterBright, it turns out it's not reasonably feasible to do an incremental replacement. The plan instead is to develop `__typeid` separately from the built-in `typeid`, and replace...

Blocked by: * https://issues.dlang.org/show_bug.cgi?id=21141 * https://issues.dlang.org/show_bug.cgi?id=21142 * https://issues.dlang.org/show_bug.cgi?id=21143 * https://issues.dlang.org/show_bug.cgi?id=21144 * https://issues.dlang.org/show_bug.cgi?id=21145 * https://issues.dlang.org/show_bug.cgi?id=21146

Though not very explicit, the current ebook is meant for the spec only. So probably that settles it without a need to discuss other pros and cons.

Oh, and we can always create more ebooks :). E.g. would be nice to have the library doc as an ebook.

This is nice if we manage to make it unambiguous.

@JinShil the destructors in Higgs look reasonable. In what way are they broken? As a general disposition, we're going toward more, not less, safety. So the situation in which we...

@JinShil thanks for asking! :) I think the intent is what we need; of course it can be improved, and also the implementation may have issues. So feedback is welcome....

@ntrel we won't cater to people relying on undocumented behavior. This not only creates difficulties for this particular PR, but creates a dangerous precedent whereby we dig ourselves in bureaucracy.

@wilzbach are examples runnable just the same in both? any dead links? anything to worry about? In the past I ran quickly into some issue.