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

Add stack trace for component definition #3

Open
soareschen opened this issue Mar 5, 2015 · 0 comments
Open

Add stack trace for component definition #3

soareschen opened this issue Mar 5, 2015 · 0 comments

Comments

@soareschen
Copy link
Member

Functional programming makes it hard to find out where a quiver component is defined. The component should keep a stack trace when it is first constructed so that we can trace back the component definitions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@soareschen