Add @saferSystem

[0xEAB]

Note

This would need a DIP.

I’m not really a fan of things only accessible through magic. This experiment adds a new attribute @saferSystem that allows users to explicitly enable “safer” checks for functions.

[dlang-bot]

Thanks for your pull request, @0xEAB!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#20606"

[atilaneves]

This would indeed need a DIP but at the very least an explanation of what this even does.

[0xEAB]

but at the very least an explanation of what this even does.

It adds an attribute for the behavior that is known as “safer”. That is means it enables the very same safety checks that are currently applied to functions with no safety annotation when -preview=safer is enabled.

[0xEAB]

A lot of the implementational bloat comes down to the addition of a new storage class. The way built-in attributes are implemented is that they are picked up into a storage class which gets later translated into a “trust” level. That trust level then determines the actual checks.

[0xEAB]

Also to clarify: This PR isn’t to be taken dead serious.

I was mostly interested in running this patch against the bigger testsuite and see how it interacts with the ecosystem world – you know, those tests performed by buildkite.

My point stands, I don’t like behavior that is only accessible through magic and cannot be reapplied after changing away from the defaults. I am aware that there’s this @default idea that we have up your sleeves that would also help eliminate said inconvenience.