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

c.typecheck causes spurious cyclic errors when used in a method annotation #49

Closed
xeno-by opened this issue Jun 28, 2014 · 2 comments
Closed

c.typecheck causes spurious cyclic errors when used in a method annotation #49

xeno-by opened this issue Jun 28, 2014 · 2 comments
Assignees
@xeno-by
Labels
critical duplicate

Comments

@xeno-by
Copy link
Member

xeno-by commented Jun 28, 2014

https://twitter.com/copumpkin/status/482748250374832129
@xeno-by xeno-by added this to the 2.1.0-final milestone Jun 28, 2014
@xeno-by xeno-by self-assigned this Jun 28, 2014
@FlorianKirmaier FlorianKirmaier mentioned this issue Oct 21, 2014
Closed
@xeno-by xeno-by mentioned this issue Nov 19, 2015
Open
@xeno-by
Copy link
Member Author

xeno-by commented Nov 19, 2015

I've merged this issue into #75 and will close this issue now. If this is a blocker for you, please let me know, and we'll think of something.

@xeno-by xeno-by closed this as completed Nov 19, 2015
@ClaireNeveu
Copy link

Is there any workaround for this? We have encountered this spurious illegal cyclic reference involving class <className> when annotating objects inside a class with our Safe Config macro.

@ClaireNeveu ClaireNeveu mentioned this issue Jan 19, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xeno-by xeno-by

Labels
critical duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xeno-by @ClaireNeveu