This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
Doc - Describe setup_hint_processor using Rustdoc comments (three slashes: ///)
#58
Labels
Context: isolated
no previous knowledge of the codebase required
Difficulty: easy
anybody can understand it
Duration: 0.5 day
will take about half a day
Good First Issue
Techno: rust
rust
Type: documentation
write documentation
Milestone
Comments
Eikix
added
Type: documentation
|
Ready to go. |
jdembdr
pushed a commit
to jdembdr/cairo-foundry
that referenced
this issue
Jan 9, 2023
jdembdr
pushed a commit
to jdembdr/cairo-foundry
that referenced
this issue
Jan 9, 2023
…ashes: ///) open-dust#58 reformat
|
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI am a blockchain and DeFi developer . I am having experience of 8 months . I am currently working as a Blockchain Researcher and Developer. My Experience in programming language like Go , Rust , Java will help me to solve this issue. |
|
Could I grab this task? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In an effort of having fully documented code, we need the way we add custom hints (mocking calls, skipping instructions, expecting revert) to be documented.
In src/cli/commands/test, please proceed to comment above the
fn setup_hint_processordeclaration in an equivalent way aspub fn compileis documented.The text was updated successfully, but these errors were encountered: