Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

why can't default members be forward-declared #4485

Open
CeylonMigrationBot opened this issue Jul 9, 2015 · 2 comments
Open

why can't default members be forward-declared #4485

CeylonMigrationBot opened this issue Jul 9, 2015 · 2 comments
Labels
m-typechecker t-discussion
Milestone
1.4

Comments

@CeylonMigrationBot
Copy link

[@gavinking] The spec says that default attributes and functions can't be forward-declared, and the typechecker enforces that, but for the life of me I don't remember why. It doesn't seem like a reasonable restriction.

[Migrated from ceylon/ceylon-spec#1379]
@CeylonMigrationBot
Copy link
Author

[@gavinking] I have pushed a commit that relaxes the restriction. But is there some reason we need it?

@CeylonMigrationBot
Copy link
Author

[@gavinking]

But is there some reason we need it?

Yes: see #4519.

@CeylonMigrationBot CeylonMigrationBot added this to the 1.3 milestone Nov 14, 2015
@CeylonMigrationBot CeylonMigrationBot mentioned this issue Nov 14, 2015
Closed
gavinking added a commit that referenced this issue Nov 14, 2015
@gavinking
relax restriction in #4485
8f6254a 
fix a bug in detection of start of declaration section
gavinking added a commit that referenced this issue Nov 14, 2015
@gavinking
fix bug #4519 by rolling back proposed change #4485
cf97766
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
m-typechecker t-discussion
Projects
None yet
Milestone
1.4
Development

No branches or pull requests
3 participants
@gavinking @quintesse @CeylonMigrationBot