[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] Inheritance of the "type" keyname: standpoint for TOSCA v1.2/v1.3?
Thanks Tal, comments in-line: From: Tal Liron <tliron@redhat.com>
On Wed, Aug 26, 2020 at 6:23 PM Chris Lauwers <lauwers@ubicity.com> wrote:
I would combine these two points together and say that the "type" keyword is conditional on whether it is a refinement or not. By the way, the issue is not only whether you need to specify "type" or not but also
what values are possible (must be the same or a derivation of the parent type). Agreed. Thatâs what I meant by âcompatibleâ type.
This bothers me. I can understand the situation of *some* functions allowing a type to be discovered ad hoc, but I do not like the idea of potentially untyped values. One of TOSCA's best features is that it is strictly
typed, and I worry about loopholes. I think we should go back to actual use cases and try to look through the problems we are trying to solve here. Perhaps there is a better solution that would not require untyped parameters? Or, we can specify very
carefully how function return values transfer types? The point I was trying to make is that parameters are (almost?) never untyped, even when there is not type keyword specified. I would call them âimplicitlyâ typed (since the type can easily be derived). Yes, letâs
work through some use cases to verify this. I believe if one has to specify both an (implicitly typed) value as well as an explicit type, this would be a violation of DRY.
Thanks, Chris |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]