Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify difference between types and type descriptors #11

Closed
jclark opened this issue Mar 20, 2019 · 3 comments
Closed

Clarify difference between types and type descriptors #11

jclark opened this issue Mar 20, 2019 · 3 comments
Labels
Area/Lang Relates to the Ballerina language specification spec/unclear Spec does not clearly explain the design
Milestone
2019R1

Comments

@jclark
Copy link
Collaborator

jclark commented Mar 20, 2019

The spec has not been sufficiently clear about the difference between types and type descriptors. Some points still need to be clarified:

  • concept that type descriptors get resolved as part of evaluation
  • inherent type is actually type descriptor
  • contextually expected type is actually type descriptor
@jclark jclark added this to the 2019R1 milestone Mar 20, 2019
@jclark jclark mentioned this issue Mar 20, 2019
Closed
@jclark jclark added Area/Lang Relates to the Ballerina language specification spec/unclear Spec does not clearly explain the design labels Mar 24, 2019
@jclark
Copy link
Collaborator Author

jclark commented Mar 26, 2019

Also need to explain evaluation of type descriptors.

@jclark
Copy link
Collaborator Author

jclark commented Mar 30, 2019

Also need to explain when contextually expected type is set. Simple cases are:

  • initializer
  • type cast
  • assignment
  • function call

More complicated:

  • fields in a constructor

jclark added a commit that referenced this issue Apr 1, 2019
@jclark
More clarity about contextually expected type
0a35429 
Part of issue #11.
jclark added a commit that referenced this issue Apr 1, 2019
@jclark
Improved design for named and default function arguments
f9ca76c 
Fixes #27, #25, #26. Starts on #33 and #28. Finishes #11.
@jclark
Copy link
Collaborator Author

jclark commented Apr 1, 2019

Enough for now.

@jclark jclark closed this as completed Apr 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area/Lang Relates to the Ballerina language specification spec/unclear Spec does not clearly explain the design
Projects
None yet
Milestone
2019R1
Development

No branches or pull requests
1 participant
@jclark