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

Update for new type constructors #86

Open
6 tasks
lucaswerkmeister opened this issue May 22, 2015 · 9 comments
Open
6 tasks

Update for new type constructors #86

lucaswerkmeister opened this issue May 22, 2015 · 9 comments
Assignees
Labels
Milestone

Comments

@lucaswerkmeister
Copy link
Member

  • type constructors (<T> => X<T>), including type constraints
  • anonymous generic functions (<T>(T t) => t), including type constraints
  • type parameters with type parameters
  • callable parameters with type parameters
  • named argument functions with type parameters
  • lazy specifications with type parameters (tt<T>(T t) => t)
@lucaswerkmeister lucaswerkmeister self-assigned this May 22, 2015
@lucaswerkmeister lucaswerkmeister added this to the 1.1.5 milestone May 22, 2015
@gavinking
Copy link
Member

Also a type parameter can now have type parameters of its own.

And don't forget that all these things can have type constraints.

@lucaswerkmeister
Copy link
Member Author

Thanks, updated the issue

@lucaswerkmeister
Copy link
Member Author

Also a type parameter can now have type parameters of its own.

Actually, I can’t find this in Ceylon.g or in the typeconstructors.ceylon test; what do type parameters with type parameters look like?

@lucaswerkmeister
Copy link
Member Author

Ooh, I see, it’s given Box<Value>, in the constraint list.

@lucaswerkmeister
Copy link
Member Author

@gavinking are type constructors still an “experimental feature” in 1.2? If yes, I’ll slip this.

@gavinking
Copy link
Member

Yes.

@lucaswerkmeister lucaswerkmeister modified the milestones: Postponed, 1.2.0 Sep 18, 2015
@jvasileff
Copy link
Member

@lucaswerkmeister when you do take this on, can you consider doing it in a feature branch for 1.2? I certainly don't want to push you into extra work, so if this doesn't make sense when the time comes, please disregard.

@lucaswerkmeister
Copy link
Member Author

The main reason I like to wait for the spec is that ceylon.ast types are usually named the same as their corresponding spec rules, but if the spec hasn’t been written yet, there’s the danger that I’ll have to rename the ceylon.ast node later.

Other than that… I’m not sure what your asking. Do you mean when I get around to adding type constructors, I should do it on a branch based on the 1.2 tag rather than whatever master is at the time, so you can build yourself a version that’s just 1.2 plus type constructors? I can do that, sure.

@jvasileff
Copy link
Member

Yes, cool, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants