Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Discussion: Rust support in CDT Cloud

Open
#44 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, vscode
Domain
cloud, devtools

Research direction

Start by reviewing the listed CDT Cloud capabilities and components, including Compile&Run, toolchain management, Trace Compass Cloud, the GDG Adapter, and the VS Code inspectors. Compare what Rust support each component currently has, using the existing Rust language analyzer as context. Done means the component-by-component support questions have explicit answers and a direction is recorded.

Written by the indexing model from the issue text.

Description

This is an introduction to discussion about Rust support in CDT Cloud.

There is a general and a number of concrete questions.

A general question is: what is CDT Cloud? Is it an IDE for C/C++ languages, or is it an IDE for system languages? In the former case, Rust is not needed, in the latter case, Rust should be included.

A number of concrete questions is about support of Rust by CDT Cloud components. For sure, Rust requires own language analyzer, but there is already quite a good one. So the question is if the component of CDT Cloud will be working with and useful for Rust, or new/replacement components should be written. Let's start with an explicit list of components and add information about their support of Rust as it becomes available.

  • CDT Cloud capabilities
    ** Compile&Run project
    ** Manage toolchains?
  • Trace Compass Cloud
  • CDT GDG Adapter
  • VS Code Memory Inspector
  • VS Code Peripheral Inspector
  • VS Code Serial Monitor

Your opinions are very welcome.

Dominant language
No language data
Stars
18
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-cdt-cloud/cdt-cloud

All issues in eclipse-cdt-cloud/cdt-cloud

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.