-
Notifications
You must be signed in to change notification settings - Fork 9
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
672 Add documentation #692
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #692 +/- ##
========================================
Coverage 80.66% 80.67%
========================================
Files 355 355
Lines 11184 11184
========================================
+ Hits 9022 9023 +1
+ Misses 2162 2161 -1
|
771b909
to
94977d3
Compare
Who is the target audience for this documentation? |
End users of the VT api. For immediate purposes, the auditors. Also, people we bring on board who want to learn VT. |
7bed070
to
f516d7b
Compare
deebc0a
to
e2664e7
Compare
@PhilMiller Please have a look. I think I've made all the necessary changes or created issues for problems I don't want to tackle in this PR. |
Revisiting it all now |
@@ -207,7 +209,7 @@ struct Scheduler : runtime::component::Component<Scheduler> { | |||
void printMemoryUsage(); | |||
|
|||
/** | |||
* \brief Enqueue a action associated with a prioritized message. The action | |||
* \brief Enqueue an action associated with a prioritized message. The action | |||
* will be enqueued with the priority found on the message. | |||
* | |||
* \param[in] msg the message |
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.
I just realized that these enqueue
overloads taking message arguments are kinda quirky wrappers to do
enqueue(getPriority(msg), action)
. I find only a single non-test call site, in messaging/active.cc
Here is an overview of what got changed by this pull request: Issues
======
+ Solved 22
See the complete overview on Codacy |
- sendMsg accepting MsgT*& now reassigns the pointer to null.
Fixes #672
Finally done... Docs for all components in VT. All the meta-docs pages for DARMA website.
You won't be able to see all the nice generated documentation until this gets merged. The auto-build will generate the docs publicly once that happens. Here's screenshot of what the home page looks like:
When it's merged, it will end up here: https://darma-tasking.github.io/docs/html/index.html
Introduction to VT:
The tutorial: