-
Notifications
You must be signed in to change notification settings - Fork 49
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
Rewrite the docs #389
Rewrite the docs #389
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At long last (looong last), this is almost ready. I need to work through one of the demos ("Using @snoop_inference
to improve inferability") and likely fix some issues at the end, but otherwise I think this is ready for anyone who wants to review it.
You can click on the |
Hmm, Documenter seems like it might have trouble until we register this 😢 . Specifically, the lines in the documentation that encourage you to |
OK, should be working now. Thanks to @asinghvi17! |
Switches from darts to blackjack. There were several features about the darts example that made for poor teaching, including the gap between `@enum` and a `struct` and the artificiality of not extending the base package. Also polishes the explanations and improves how things are named.
This is intended to encourage users to collect data with just SnoopCompileCore.
OK, I think this is finally ready. I anticipate merging and releasing SnoopCompile 3.0.0 later today. |
This aims to rewrite the documentation loosely in the style advocated by divio.
It acknowledges the existence of PrecompileTools and focuses on how you use SnoopCompile to understand why precompilation isn't working the way you'd like.