Disable all anti work keywords on a fundamental level. immutable @safe private when passed a flag.

On Sunday, 13 July 2025 at 00:12:16 UTC, Monkyyy wrote:

Hey! Private is useful :(

On Sunday, 13 July 2025 at 00:52:56 UTC, Kapendev wrote:

False; it can only make less code work. I understand that some have a religious belief that some working code is unholy. However I would prefer my computer does what I tell it to do when I tell it to do it and not do major reworks if I happen to use code with such unnecessary wounds.

On Sunday, 13 July 2025 at 01:07:28 UTC, monkyyy wrote:

I do think that having private struct/class fields is sometimes annoying, but nothing wrong with private functions.

On Sunday, 13 July 2025 at 08:47:30 UTC, Kapendev wrote:

https://forum.dlang.org/thread/xpmcikgbxhwnraglzbsf@forum.dlang.org?page=1

I one symbol typo can cause many problems

On Sunday, 13 July 2025 at 01:07:28 UTC, monkyyy wrote:

Then again, probably you agree there is some code you wouldn't want to compile. If I write

SpamSpamSpam$% }}}123€([//
øÅ  @rgmh**^||

do you think that should compile to something? If not, there you have it - there is code that shouldn't work.

The question is, where are you drawing the line - when do compiler checks go too far?

On Sunday, 13 July 2025 at 08:47:30 UTC, Kapendev wrote:

private is bad, grouping private: is even worse, it makes people write bad software, you should focus on optimizing your memory layouts, field order is important

On Thursday, 17 July 2025 at 13:53:24 UTC, Dukc wrote:

SpamSpamSpam$% }}}123€([//
øÅ  @rgmh**^||

Failing to parse is different from not working because extra code decides its a bad idea; my line would be mostly ()'s matching and semicolons for compiled c-like languages; in a calculator every string should return a result.