Skip to content
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.

Sign up for GitHub

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

Add support for the Rust language #102

Open
wants to merge 15 commits into
base: development
Choose a base branch
from
Open

Add support for the Rust language #102

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
15 commits
Select commit Hold shift + click to select a range
b41661a
Merge pull request #89 from IEEE-NITK/development
adityachirania Mar 23, 2022
4b7f47b
Merge pull request #92 from IEEE-NITK/development
Dragonado Mar 26, 2022
23f070b
1.4.0
Dragonado Mar 26, 2022
548cef4
1.5.0
Dragonado Mar 26, 2022
6d1e10c
update README
Dragonado Mar 26, 2022
e1ee570
1.6.0
Dragonado Mar 26, 2022
c24de76
Add haskell partial-support.
Dragonado Jul 25, 2022
fcf9c8c
change README for haskell support
Dragonado Jul 25, 2022
692c298
Add problem folder creation support for haskell
Dragonado Jul 26, 2022
8417b12
Fix test case parsing issue with new CF testcase highlighting
Dragonado Aug 16, 2022
91be16a
Merge pull request #96 from Dragonado/master
adityachirania Aug 19, 2022
f353617
1.7.0
Dragonado Aug 19, 2022
7708e65
Added support for Rust language
Jan 20, 2023
397baf0
Removed "problem matcher" dependency
royalpinto007 Jan 22, 2023
a2a2175
Merged Rust compilation into existing case
royalpinto007 Jan 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 13 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ A Visual Studio Code Extension to help **Codeforces** Users ***Code with Conveni
- Java (compiler : javac)
- Python
- Kotlin
- Haskell (compiler: ghc) [stress testing is not supported]
- Rust [stress testing is not supported]
- Note : You may add additional compilation flags through the codepal settings (example : -std=c++14) and also choose between python, python2 or python3 depending upon the python command you use on your system to run.

# Operating Systems Supported
Expand Down Expand Up @@ -101,19 +103,19 @@ Below are the various clickable icons used in our extension.
## Usage Guide to Various Features

### 1. Filtering Problems
- Click on icon **5** (shown [here](#labels)) to filter the problem set.
- Click on icon **7** (shown [here](#labels)) to filter the problem set.
- Add the lower bound for problem’s rating. (Default lower bound is 0)
- Add the upper bound for problem’s rating. (Default upper bound is 4000)
- Tick the tags you want for the problems. (If no tags are selected, no tag-based filtering is done)
- Tick the submission status of the problems you want to view.

### 2. Creating Problem Folder
- Click on icon **6** (shown [here](#labels)) beside the problem name to create and open a problem folder containing the solution file and test cases. (Make sure you have opened a folder on VS Code where you want the problem folder)
- Click on icon **11** (shown [here](#labels)) beside the problem name to create and open a problem folder containing the solution file and test cases. (Make sure you have opened a folder on VS Code where you want the problem folder)

### 3. Creating Contest Folder
- Click on the type of contest you want to participate in. (Past, Running or Future)
- Precise timings and durations of upcoming contests are also shown.
- Click on icon **3** (shown [here](#labels)) beside the contest name to create and open a contest folder containing the problems folders of each problem of the contest. (Make sure you have opened a folder on VS Code where you want the contest folder)
- Click on icon **5** (shown [here](#labels)) beside the contest name to create and open a contest folder containing the problems folders of each problem of the contest. (Make sure you have opened a folder on VS Code where you want the contest folder)

### 4. Adding Your Own Code Template
- Press *Ctrl + comma(,)* or go to settings of VS Code (icon on bottom left).
Expand All @@ -124,21 +126,21 @@ Below are the various clickable icons used in our extension.
- Go to extensions and select codepal, and choose the compiler you want from the drop down list.

### 6. Adding Test Cases
- Click on icon **7** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + A*, to add manual test cases for the problem.
- Click on icon **13** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + A*, to add manual test cases for the problem.

### 7. Running Test Cases
- Click on icon **10** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + R*, to run the code for all sample and manual test cases.
- Click on icon **18** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + R*, to run the code for all sample and manual test cases.

### 8. Viewing Problem
- Click on icon **9** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + O*, to open the problem statement on Codeforces in your default browser.
- Click on icon **17** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + O*, to open the problem statement on Codeforces in your default browser.

### 9. Submitting Problem
- Click on icon **12** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + S*, to open the submission page of the problem on Codeforces in your default browser.
- Click on icon **20** (shown [here](#labels)) on the top right side of the editor window, or press *Ctrl + Alt + S*, to open the submission page of the problem on Codeforces in your default browser.

### 10. Stress Testing
- Click on icon **8** (shown [here](#labels)) on the top right side of the editor window to create the stress testing files called "brute" and "gen". Here "brute" is the code that is a bruteforce solution or any code that gives the correct output and "gen" is the generator file that makes testcases. You need to code both of them.
- Click on icon **15** (shown [here](#labels)) on the top right side of the editor window to create the stress testing files called "brute" and "gen". Here "brute" is the code that is a bruteforce solution or any code that gives the correct output and "gen" is the generator file that makes testcases. You need to code both of them.
- Command line arguments of integers (1,2,3...) are passed to the generator file so as to keep a fixed random seed each time you stress test. A template is initially provided that takes care of this.
- Once all 3 files compile properly (solution, "brute" and "gen" files) click on icon **11** (shown [here](#labels)), or press *Ctrl + Alt + Z*, to stress test. It will run the "gen" file to create input and compare it against your solution and "brute". If they differ then it is reported else it moves to the next case. By defualt it will run for a number of 100 test cases but this can be changed in the settings.
- Once all 3 files compile properly (solution, "brute" and "gen" files) click on icon **19** (shown [here](#labels)), or press *Ctrl + Alt + Z*, to stress test. It will run the "gen" file to create input and compare it against your solution and "brute". If they differ then it is reported else it moves to the next case. By defualt it will run for a number of 100 test cases but this can be changed in the settings.
- Stress testing can be forced to stop on pressing *Ctrl + Shift + Z*.

### 11. User Profile
Expand All @@ -152,8 +154,8 @@ Below are the various clickable icons used in our extension.
- Go to extensions and select codepal, and check the "Enable Atcoder Library Support" checkbox.
- Go to extensions and select codepal, and check the "Enable Atcoder Documentation Button" checkbox if you want that button to be visible in the menu.
- You can now use the atcoder library header files (for eg, "#include <atcoder/all>") without any extra setup.
- To submit on Online Judges that don't support ACL (atcoder library), you can click on icon **13** (shown [here](#labels)). This creates a new file called "combined.cpp" that includes all the atcoder header files used explicitly. You can now submit "combined.cpp" on any Online Judge. For more information check [here](https://atcoder.github.io/ac-library/production/document_en/appendix.html).
- To read the ACL documentation you can click on icon **14** (shown [here](#labels)) if you have enabled it in settings.
- To submit on Online Judges that don't support ACL (atcoder library), you can click on icon **14** (shown [here](#labels)). This creates a new file called "combined.cpp" that includes all the atcoder header files used explicitly. You can now submit "combined.cpp" on any Online Judge. For more information check [here](https://atcoder.github.io/ac-library/production/document_en/appendix.html).
- To read the ACL documentation you can click on icon **16** (shown [here](#labels)) if you have enabled it in settings.

### 13. C++ Intellisense autocomplete support for Atcoder Library
- Download the "atcoder" folder from [here](https://github.com/atcoder/ac-library). Copy the file path of "atcoder" folder in your local system.
Expand Down
Loading