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

implements #144

Closed
satyr opened this issue Jul 2, 2012 · 3 comments
Closed

implements #144

satyr opened this issue Jul 2, 2012 · 3 comments

Comments

@satyr
Copy link
Owner

satyr commented Jul 2, 2012

class C implements D, E
  ...

would roughly be equal to:

class C
  prototype <<<< D
            <<<< E
  ...

<<<< over <<< for flattening.

@apaleslimghost
Copy link

Might lead people to expect interfaces. How about a Scala-like class C extends D with E?

@satyr
Copy link
Owner Author

satyr commented Jul 2, 2012

Might lead people to expect interfaces.

Interfaces as in Java don't make much sense without static typing though. I think implements for mixins/traits works since the goal--providing additional sets of behaviors--is the same. It's already reserved, so we can make use of it with no drawbacks.

How about a Scala-like class C extends D with E?

Wouldn't parse because:

$ coco -bce 'D with E then'
D((function(){}.call(E)));

is already valid.

@vendethiel
Copy link
Contributor

Really interesting

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

3 participants