ENGN3712 (Rust Research Project with Alex Potanin and Ilya Sergey). Bringing extract method refactoring to the rust programming language.

This repository contains both of the reports for the project, as well as the code that was written for the project (through the submodules).

Structure

This repository contains the following directories:

• artefacts: Contains the artefacts linked to this project. Concrete, runnable examples of the code that was written for the project.
• examples: Contains example uses of the code, alongside examples included in the reports.
• experiments: Contains experimental code used to test concepts and ideas.
• rem: Contains the Rust-Extraction-Maestro (REM) toolchain. This is the main codebase for the project.
• reports: Contains the reports for the project (both the final report and the interim report).

Artefacts

Examples

Experiments

• rust-lsp-test <git = https://github.com/RuleBrittonica/rust-lsp-test (private)> - A test of the rust language server protocol

REM

• rem-borrower <git = https://github.com/RuleBrittonica/rem-borrower> (Availble from the crates.io registry)
• rem-cli <git = https://github.com/RuleBrittonica/rem-cli>
• rem-constraint <git = https://github.com/RuleBrittonica/rem-constraint> (Availble from the crates.io registry)
• rem-controller <git = https://github.com/RuleBrittonica/rem-controller> (Availble from the crates.io registry)
• rem-extract <git = https://github.com/RuleBrittonica/rem-extract> (Availble from the crates.io registry)
• rem-repairer <git = https://github.com/RuleBrittonica/rem-repairer> (Availble from the crates.io registry)
• rem-testfiles <git = https://github.com/RuleBrittonica/rem-testfiles>
• rem-utils <git = https://github.com/RuleBrittonica/rem-utils> (Availble from the crates.io registry)
• rem-vscode <git = https://github.com/RuleBrittonica/rem-vscode> (Also available from the Visual Studio Code marketplace)

Reports

• enivironment test: Ensure that the latex environment builds correctly
• mid_semester: (Due Friday week 12, semsester 2, 2024) A report on the progress of the project
• final: (Due Friday week 12, semester 1, 2025) The final report for the project