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.

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

Type system #62

Closed
emil14 opened this issue Mar 14, 2022 · 2 comments
Closed

Type system #62

emil14 opened this issue Mar 14, 2022 · 2 comments

Comments

@emil14
Copy link
Collaborator

emil14 commented Mar 14, 2022

Context

Implement type-system compatible with most common languages like json, yaml, graphql and protobuf.
Type-system must be strong enough to make compiler available check most dangerous errors and compete golang.
Question that must be answered:

  • What is type?
  • How many built-in types do we have?
  • Is it possible for used to create its own type?
  • Is it possible to have generic type?
  • What's the algorithm of checking whether two types are compatible?
    • Is this duck, gradual or nominative typing?

Related to #39 and #77

@emil14
Copy link
Collaborator Author

emil14 commented Apr 11, 2022

Base type idea

J.P.Morrison writes about logical and physical type of data. This is something like implementation vs API. It's also has something similar to how Go handle its types - user defined type has defined behavior (methods) and base type

Problems

  • There's no behavior in FBP. Messages (IPs) are not OOP-objects, they just data. So their API is

@emil14 emil14 mentioned this issue Sep 18, 2022
@emil14
Copy link
Collaborator Author

emil14 commented Nov 8, 2022

Moved to #99

@emil14 emil14 closed this as completed Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant