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

support tracing of the plugin's conversion #51

Open
zliu41 opened this issue Apr 15, 2022 · 0 comments
Open

support tracing of the plugin's conversion #51

zliu41 opened this issue Apr 15, 2022 · 0 comments

Comments

@zliu41
Copy link
Member

zliu41 commented Apr 15, 2022

There is a change up with a crude version of this, but it needs to be more comprehensive and more controllable

a number of improvements we should make:

  • control these via plugin flags (already done)
  • convert to general levels and/or categories
  • distinguish between plugin-user debugging (what instance am I missing?) and plugin-dev debugging (why didn't it find the instance that exists?)
  • optionally only output on a failure
  • replace trace with something Writer-y (which also makes output-on- failure feasible)
  • take advantage of trampolining to do this in a single place
  • trampolining (which we already need for the conversion) gives us a middle ground between an opaque fold and recursion-scheme level introspection.
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

1 participant