-
Notifications
You must be signed in to change notification settings - Fork 20
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
ProTrace mod #684
Comments
I have no idea what this is, but I am happy to help :D |
I am glad to hear it! Would be more than happy to explain my ideas and also go through existing tracing functionality. |
Yeah, sure! Please go ahead |
Wait sorry, I was meant to assign this to someone else. |
Really sorry for the confusion. But if you also want to get involved, I would be more than happy to talk to you. Are you a part this semester VIP team or previous ones? |
No worries at all! I’d love to get involved. I thought this might be really interesting. I’m not part of the VIP team this semester, but I was maintaining the CP demos before. I saw the documentation above. Would you like to walk me through your implementation or anything? |
One small thought (and I'm not saying do this, it's just a thought :) ) Do you want to be able to report the "kind" of message, as well as the verbosity level? Lots of tracing libraries support the ability to specify the 'type' of message, someone might (for example) want to see all the rules to do with type refinement, but nothing else. I don't know in this case if it's worth trying to sort messages by both verbosity and kind, but it possible worth thinking about it and explictly saying it isn't happening :) |
O, that is a good idea! I will definitely add it as a potential future feature. |
Are you still in St Andrews? |
An idea for internal implementation for all the tracing functionality in a form of a Rust module
ProTrace.
The first draft of the design document is linked below.
DesignDoc (ProTrace).docx
The text was updated successfully, but these errors were encountered: