Special ProjectsNot StartedQuantum Red theme

QWArcT*

QWArcT* is a specification for a new programming language and developer-tooling ecosystem. The design includes explicitly named numeric types, object-oriented classes, access zones, headers/source files, constructors, destructors and scope resolution. Future phases cover a compiler, runtime, QWA libraries, IDE tooling and interoperability with C++, Qt, .NET and Q#; the language is not yet implemented.

QWArcT*C++Qt 6Q#LLVM
QWQWArcT*
QWArcT*Main technology
1Tracked files*
1.md files
--Additional metric
01 · What it does

Planned capabilities

Roadmap goals, not shipped software.

01

Explicit data types such as int32, int64, float32 an

Explicit data types such as int32, int64, float32 and float64. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02

Class declarations with configurable access zones an

Class declarations with configurable access zones and modifiers. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

03

Planned headers, source files, constructors, destruc

Planned headers, source files, constructors, destructors and scope resolution. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04

Planned compiler, runtime, standard library and stud

Planned compiler, runtime, standard library and studio tooling. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Technical structure

How the system works

Planned component boundaries and data flow.

01

The README describes a proposed modular architecture. No executable implementation is verified in the repository.

01 · Input or user action

The workflow starts with the corresponding user choice or data entry. Explicit data types such as int32, int64, float32 and float64. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Application processing

The relevant component must interpret the input, apply the project rules and coordinate any necessary storage, network access or computation. The documentation below identifies where that responsibility appears in the source when it is evidenced.

03 · Result and feedback

The resulting screen, calculation or stored record should reflect the processed state. Planned headers, source files, constructors, destructors and scope resolution. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04 · Boundaries and verification

This page describes the documented behaviour, not an independently verified live deployment. Runtime configuration, permissions, test data or connected services may still be required.

PROJECT WALKTHROUGH

Design & planned systems

Concept modules described in the product roadmap.

01

Language syntax — specification

The QWT proposal uses explicit types such as int32, int64, float32 and float64, class members, access zones and named functions with a recognisable C++-influenced structure.

02

Classes and lifecycle — specification

The design describes constructors, destructors, access modifiers, inheritance and virtual methods, alongside more explicit rules for scope resolution and declaration files.

03

Interoperability — planned

Future adapters would connect C++, Qt, C#/.NET and Q# capabilities without implying that all foreign runtimes share one ABI or ownership model.

04

Compiler and tools — planned

The proposed roadmap includes parsing, semantic analysis, intermediate representation, an early C++ transpilation path, standard libraries and QWArcT Studio.

05

UI and tooling ecosystem — planned

A declarative UI layer, visual designer, editor services and user-created packages are part of the longer-term developer experience.

03 · Explore

Project-specific preview

A project-specific web demo may be added later. This page currently prioritizes verified screenshots and source-backed descriptions.

Visual studies · project-specific

Interface and system concepts

Independent illustrative views of the documented or proposed workflows. They are not connected to a running backend, and their values are not actual measurements.

Planned compiler interface · illustrative

Language source and diagnostics

1  module Studio;
2  public int32 main() {
3    return 0;
4  }
Parser ✓
Types ✓
Diagnostics · 0

The proposed toolchain reads source files, checks syntax and types and explains compilation diagnostics.

Source .qwtTokensParserDiagnostics
Planned project explorer · illustrative

Module and header relationships

Headers
Source files
Imports
Compiler

Separating declarations, implementations and modules keeps the planned language ecosystem easier to inspect and extend.

HeadersSource filesImportsCompiler
04 · Source and design

Implementation examples and code walkthrough

Illustrative design-only code. This is not part of an implemented or executable application.

Proposed syntax from the design specification — not executable

README.md / language specification v0.4Design-only illustration
QWT
import QWA.Core;
QWTClass QWA_Calculator {
    QWT-Zone { Public } {
        int32 QWA-Aduna(int32 QWA_A, int32 QWA_B) {
            return QWA_A + QWA_B;
        }
    }
}

Code samples are excerpts or documented illustrations; surrounding project files, configuration and dependencies may be required to compile or run them.

06 · Technology

Programming languages & stack

QWArcT*
C++
Qt 6
Q#
LLVM

Core technologies and integrations used or planned for this project.

File types identified: 1 .md

07 · Reality check

Status, evidence & limitations

The project status is based on repository sources and supplied documentation. It may be updated as the project evolves. A published case study is not a certification of production readiness.
  • The specification does not constitute a functional compiler or production language toolchain.
08 · Resources

Downloads & project resources

Installers appear only after a verified release is added to the public download directory. Unavailable builds are marked clearly.

↓Windows EXEComing soon↓Android APKComing soon
For this concept, there is currently no executable release. Desktop and Android package placeholders are shown until verified releases are published.