-
Notifications
You must be signed in to change notification settings - Fork 4
Documentation tracking issue! #25
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
Comments
A few questions: A few questions: How do I document: function MMI.predict_mean(model::LinearBinaryClassifier, (fitresult, _), Xnew) and function MMI.predict(model::LinearBinaryClassifier, (fitresult, decode), Xnew) ? Is there a reason we preemptively unpack this iterable instead of having one named parameter the function takes in and then unpacking it internally? Secondarily, at what point do we go from: """
function foo(X, y, z)
blurb
""" to """
function foo(X, y, z)
blurb
# Arguments
- `X`:
- ....
""" I am relatively new to julia and this has been bothering me for a bit :) |
You don't. See comments at #26
I guess this is mainly a style point. I doubt it will compile any differently either way.
Yeah good question. Personally, I usually unpack the options when they no longer fit on one line of the doc-header. There is a style guide that we say we adopt: https://github.com/invenia/BlueStyle Maybe it says there. In the case of the current documentation roll-out though, this point is mute. You always unpack the options (hyper-parameters) in a model doc-string |
Ah this is super helpful! I will read through this more closely! |
The text was updated successfully, but these errors were encountered: