Andrei Alexandrescu

e.g. https://dlang.org/library-prerelease/ has a few oddities: * Table has a wide first column due to large module names such as `std.experimental.allocator.building_blocks.affix_allocator`. I think we could insert a soft break before...

I also don't see any runnable test. Do we need to do some deployment? @CyberShadow is ddox part of the auto-deployment engine?

Copying from my older comments: "...e.g. https://dlang.org/library-prerelease/ has a few oddities: ..." * Table has a wide first column due to large module names such as `std.experimental.allocator.building_blocks.affix_allocator`. I think we...

I'd say let disqus be. Doesn't hurt and the dearth of comments is not a reflection on disqus as much as a lack of critical mass in viewership.

>We should do a Phobos PR to add some description text to those modules. Correct, those should ideally predate switching to ddox.

This goes on to confirm what I like to joke about: whatever we do, someone will be against it. Page-per-artifact has been vociferously asked for by many folks. Growing pains!...

Only regular flowing text should be justified, nothing else (not even tables) btw.

A pragma sounds nice, too. It would solve the composition problem that this DIP has: Consider two pure functions `f(int)` and `g(int)`. Then `f(42)` is CTFE, `g(42)` is CTFE, but...

Got to add that determining CTFEability based on the function and call seems at least on the surface a more principled approach than a pragma. Also, it will CTFE existing...

@WalterBright cool, all I'm saying is that the depth-first folding would be good to mention in the DIP in addition to here. Just paste your text there! :)