On Sunday, 5 March 2017 at 05:45:19 UTC, Ilya Yaroshenko wrote:
>
> I don't care about existing D users. Sorry about that. In the same time I do not see any problem with betterC for existing D users. Any betterC library can be used with Druntime like either a common C library or generic D library.
>

But you're not going to convince any existing D users with that attitude.

Ilya Yaroshenko wrote:

> I don't care about existing D users.

i wonder if "existing D users" care about your "betterC" and other initiatives then.

rethorical sentence, no need to answer to it.

On 4/03/2017 7:10 PM, Patrick Schluter wrote:
> The compiler front-end did just that. I can not comment on the quality
> of the code but on the speed of compilation, wow, just wow.
>
> Building v2.067 takes 1'38" on the server at work (westmere at 2.2 GHz,
> gcc 6.2, dmd v2.073, single core build).
> Building v2.073 takes 0'15" and most of that time is taken by building
> the backend which is still in C++.
> If that were rewritten in D, I suppose building the compiler would take
> 2 or 3 seconds max.

Yup.  And the same exact approach would be applicable to many other large C++ projects.  Most would be easier than converting the D compiler, because a huge part of the work was perfectly matching the C++ ABI so the glue layer/backend could still be in C++.

I did consider trying this with some other projects but there really aren't any large C++ projects I work with frequently enough for this to be worth the time.  LLVM would probably be a good project, but without someone to maintain the fork and zero chance of switching upstream to D, there isn't much point.

It's worth noting that maintaining an automatically converted fork is much much less work than maintaining a manually converted fork.

On Saturday, 4 March 2017 at 07:09:17 UTC, Nick Sabalausky (Abscissa) wrote:
> In a similar vein, I have to say I'm thoroughly impressed with what I've learned of Mir. AIUI, aside from being a fantastic lib, it looks like a tool with very high widespread potential that's written in D, yet also targets, more or less, C/C++ users in addition to D users. A tactic I've definitely been in favor of[1] and would love to see pushed as far as it can go.

Is Mir available as both D and C++ source?

On Thursday, 9 March 2017 at 17:31:53 UTC, Ola Fosheim Grøstad wrote:
> On Saturday, 4 March 2017 at 07:09:17 UTC, Nick Sabalausky (Abscissa) wrote:
>> In a similar vein, I have to say I'm thoroughly impressed with what I've learned of Mir. AIUI, aside from being a fantastic lib, it looks like a tool with very high widespread potential that's written in D, yet also targets, more or less, C/C++ users in addition to D users. A tactic I've definitely been in favor of[1] and would love to see pushed as far as it can go.
>
> Is Mir available as both D and C++ source?

Mir written in D. mir-cpuid and mir-glas has extern(C) ABI, mir-algorithm (ndslice) is generic and be used to write extern(C) libraries.