Re: Discriminants or Constructor Function for Limited Types

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2022-05-05 01:49, Randy Brukardt wrote:

> Those cases that you worry are "unsafe" seem to me to only occur because of
> "hacks and workarounds". There's no good reason to do any of those things
> intentionally unless you are using a "hack" to do something dubious in the
> first place.

Is a task component a hack? Well so long there is no tagged task types 
aggregation is the only way.

Controlled types are hacks, yes, but there is no alternative. You admit 
that all tagged types (and I would say all types) should be controlled = 
support user-defined initialization hooks.

Dispatching from Initialize is a double hack, but again, if you need it, 
the alternative, client-side manual initialization is way worse.

Exception propagation upon initialization? There is no enforceable 
exception contracts to fight it.

So I say, if hacks occur, then because of the language problems, not 
only because some lazy programmer does something stupid.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de