D has become unbearable and it needs to stop

FeepingCreature feepingcreature at gmail.com
Thu Jul 6 02:44:30 UTC 2023


On Wednesday, 5 July 2023 at 23:22:14 UTC, harakim wrote:
> On Wednesday, 5 July 2023 at 10:14:38 UTC, FeepingCreature
>> Compiler flags don't work as soon as libraries come into play. 
>> Really, what you'd want is *package flags;* settings that 
>> lexically affect exactly the modules of a particular dub 
>> library.
>
> At first, I thought this made sense, but now I wonder why would 
> it be a problem? Either you're pulling the source and you can 
> compile with the flag or you're pulling the binary and it's 
> already built. It seems like it makes sense and I must be 
> missing something.

The problem is that you're committing your whole project to 
either having the flag set or not having it set. If some code 
will only work with and some code only without, you're SOL. And 
the more flags you add to the compiler, the more likely a 
conflict becomes.


More information about the Digitalmars-d mailing list