From: Mehdi Saada <00120260a@gmail.com>
Subject: Re: why "unconstrained subtype in component declaration" while said component given default value ?
Date: Sat, 26 May 2018 17:45:52 -0700 (PDT)
Date: 2018-05-26T17:45:52-07:00 [thread overview]
Message-ID: <07b99fab-714d-43a5-b8ea-c22d7e26fd80@googlegroups.com> (raw)
In-Reply-To: <71948f43-cf43-448f-a7b0-0e5982c98d90@googlegroups.com>
> What's the use-case for this?
the use case is pretty limited if the subtype of Chaine has to be constrained. But it would have been practical if it wouldn't have to.
I was just thinking on the possibility of providing diverse constrained subtype of a unconstrained/undefined type, with different defaults values.
Of course using constructor functions is easier and works very well, so there's no issue... I was just pondering.
next prev parent reply other threads:[~2018-05-27 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 21:03 why "unconstrained subtype in component declaration" while said component given default value ? Mehdi Saada
2018-05-26 21:40 ` Jere
2018-05-26 22:11 ` Mehdi Saada
2018-05-26 23:55 ` Jere
2018-05-27 0:14 ` Jere
2018-05-27 0:29 ` Mehdi Saada
2018-05-27 0:45 ` Mehdi Saada [this message]
2018-05-27 17:15 ` Shark8
2018-05-27 17:30 ` AdaMagica
2018-05-27 18:17 ` Shark8
2018-05-29 1:28 ` AdaMagica
2018-05-29 17:20 ` Mehdi Saada
2018-05-27 7:45 ` Jeffrey R. Carter
2018-05-26 23:41 ` Shark8
2018-05-27 7:07 ` Simon Wright
2018-05-27 17:22 ` Shark8
2018-05-27 12:24 ` Mehdi Saada
2018-05-29 22:28 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox