CTFE ^^ (pow)

[Norm]

On Friday, 23 March 2018 at 05:24:48 UTC, Walter Bright wrote:
> On 3/22/2018 9:15 PM, Norm wrote:
>> On Friday, 23 March 2018 at 03:28:05 UTC, Walter Bright wrote:
>>> What are the bugzilla issues on those?
>> 
>> This is just a few cut-paste from the collated list. Some were 
>> reported but found later to be duplicates, many were existing 
>> bugs, so no new bugzilla was created in those cases.
>> 
>> https://issues.dlang.org/show_bug.cgi?id=18055
>> https://issues.dlang.org/show_bug.cgi?id=17942
>> https://issues.dlang.org/show_bug.cgi?id=16317
>> https://issues.dlang.org/show_bug.cgi?id=16189
>> https://issues.dlang.org/show_bug.cgi?id=17949
>> https://issues.dlang.org/show_bug.cgi?id=15511
>> https://issues.dlang.org/show_bug.cgi?id=16107
>
> Thank you. I have tagged them with the "Industry" keyword, 
> which is for issues raised by people using D in industrial 
> situations. The last one (16107) is marked as resolved and 
> appears to have been fixed.

Thanks, sorry that was my mistake (posting in a hurry). It was 
this bug:

https://issues.dlang.org/show_bug.cgi?id=16108
(hardly what I would call a blocker, but I didn't make the list)

Looking at bugzilla I see this is also now fixed but we were on 
2.074 at the time. Sorry I don't have more specific details, it 
was hard enough just to get some devs to create bugzilla accounts 
let alone find existing tickets or raise new tickets.

As I was trying to point out before but unfortunately came across 
as just a negative git; many developers agreed that D is a 
fantastic language, but they have zero interest in developing or 
even raising tickets when D doesn't just work. I think the main 
reason for this is because they expect a C++/Python like 
experience where your rarely hit a compiler/interpreter bug.

This seems to be the majority of developers I talk to, so it is a 
hard sell, but on the bright side I'm starting to see more and 
more internal tools here written in D :)

Cheers,
Norm