-
Notifications
You must be signed in to change notification settings - Fork 137
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
Improve documentation #1765
Improve documentation #1765
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1765 +/- ##
==========================================
- Coverage 77.43% 77.43% -0.01%
==========================================
Files 306 305 -1
Lines 62442 62552 +110
==========================================
+ Hits 48355 48437 +82
- Misses 12467 12494 +27
- Partials 1620 1621 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 3db7348 Collapsed results for better readability
|
docs/language/accounts.mdx
Outdated
@@ -198,7 +198,8 @@ struct AccountKey { | |||
let isRevoked: Bool | |||
} | |||
``` | |||
Refer the [PublicKey](crypto/#publickey) section for more details on the creation and validity of public keys. | |||
|
|||
Refer the [`PublicKey` section](crypto/#publickey) for more details on the creation and validity of public keys. |
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.
Refer the [`PublicKey` section](crypto/#publickey) for more details on the creation and validity of public keys. | |
Refer to the [`PublicKey` section](crypto/#publickey) for more details on the creation and validity of public keys. |
``` | ||
|
||
It is invalid to declare a synthetic field with only a setter. | ||
Initializers do not support overloading. |
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.
Do we want to add some language here to call out that we plan on supporting this in the future? While documenting the behavior as if it exists is misleading, a statement like this may give the impression that we have no intention of ever supporting overloading at all. Perhaps something like "Initializers do not currently support overloading, but there are plans to add support for this in the future."
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.
Agreed. There aren't any plans to add support for overloading at the moment, it's just a feature I had thought we would want when writing this 3 years ago, and since then there has been no mention/discussion around it
} | ||
} | ||
``` | ||
Functions do not support overloading. |
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.
Same comments here as about initializers.
Co-authored-by: Daniel Sainati <[email protected]>
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.
Looks good!
Co-authored-by: Joshua Hannan <[email protected]>
accidentally deleted in #1765
Closes #1701
Closes #1328
Closes #1282
Closes #1237
Closes #1223
Closes #1203
Work towards #959
master
branchFiles changed
in the Github PR explorer