On Wednesday, 6 August 2025 at 00:42:43 UTC, Brother Bill wrote:
It doesn't seem like modern D needs the @disable feature.
If a struct has a user provided constructor, then the default
constructor is removed.
Are there any cases where @disable is useful in modern D?
it always seemed like a naturally extension of `@deprecate` and
deprecate isnt going anywhere; I dont even know if the `@disable
this()` was a intentional feature, it seems like a ye old
documenting what happens as if intentional.
Nothing id use, but someone has this theory that deprecation
should be a long cycle, these provide tools to auto generate
error messages and phoebes (pretends to) practice this cycle
