uncertain-lang 0.1.0__tar.gz

uncertain_lang-0.1.0/.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

uncertain_lang-0.1.0/.github/workflows/smoke-test.yml

@@ -0,0 +1,35 @@
+name: Smoke Test
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  build-and-test:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+        
+    - name: Install hatch and dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install hatch
+        
+    - name: Install package
+      run: |
+        pip install .
+        
+    - name: Run Pytest
+      run: |
+        pytest tests/
+        
+    - name: Smoke Test CLI
+      run: |
+        uncertain examples/my_experiment.calc

uncertain_lang-0.1.0/.gitignore

@@ -0,0 +1,167 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# uv
+uv.lock
+
+# IDEs and Editors
+.vscode/
+.idea/
+*.swp
+*.swo
+.DS_Store
+
+# Design Documents
+uncertain-implementation-plan.md
+uncertainty-typed-language.md

uncertain_lang-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

uncertain_lang-0.1.0/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.5
+Name: uncertain-lang
+Version: 0.1.0
+Summary: Add your description here
+Requires-Python: >=3.12
+Requires-Dist: hypothesis>=6.126.0
+Requires-Dist: numpy>=2.2.3
+Requires-Dist: pytest>=8.3.4
+Requires-Dist: uncertainties>=3.1.7
+Description-Content-Type: text/markdown
+
+# Uncertain
+
+*A statically-typed arithmetic DSL where every value's type encodes its distributional uncertainty — and the compiler proves how that uncertainty compounds.*
+
+## Why Uncertain?
+
+When you write equations for physical measurements, sensor data, or statistical variables, those values are almost never exact—they are probability distributions. 
+
+If you reuse a variable in a normal programming language without explicitly tracking its mathematical correlation (e.g. `a * a`), your calculated variance will be silently understated, leading to overconfidence in faulty data. 
+
+**`Uncertain` catches these correlation bugs at compile-time by enforcing dependency tracking in its type system.**
+
+---
+
+## Quick Start
+
+### Prerequisites
+- [uv](https://astral.sh/uv/) (Fast Python package and environment manager)
+- Python 3.12+
+
+### Installation
+
+The compiler is available on PyPI. You can install it globally via `pip` or `uv`:
+```bash
+pip install uncertain
+# or
+uv tool install uncertain
+```
+
+If you want to install from source:
+```bash
+git clone https://github.com/yourusername/uncertain.git
+cd uncertain
+pip install .
+```
+
+### Running Scripts
+
+Run an example calculation using the newly installed CLI:
+```bash
+uncertain examples/my_experiment.calc
+```
+
+---
+
+## The Hero Demo: Catching Correlation Bugs
+
+Consider this simple program:
+
+```calc
+let a = sensor_read();
+let variance_est = a * a;
+```
+
+Running `uncertain` on this file immediately catches the hidden dependency reuse:
+
+```text
+error: uncertain reuse without correlation annotation
+  --> line 2:20
+   |
+ 2 | let variance_est = a * a;
+   |                    ^^^^^ `a` appears twice in this product
+   |
+   = note: treating repeated occurrences of `a` as independent understates
+     the true variance of the result.
+   = help: use `square(a)` for the correct self-product variance formula,
+     or wrap with `correlated(..., ..., cov = ...)` if you have an explicit
+     covariance estimate.
+```
+
+### Catching Runtime Math Errors at Compile Time
+Beyond type checking, `uncertain` uses the same beautiful diagnostic system to catch mathematical domain errors before your program even evaluates. For example, taking the square root of a distribution with a negative mean:
+
+```calc
+let a = sensor_read() - 15.0;
+let b = sqrt(a);
+```
+
+Yields a pinpointed math-domain error:
+```text
+error: math domain error
+  --> line 2:9
+   |
+ 2 | let b = sqrt(a);
+   |         ^^^^^^^ invalid operation
+   |
+   = note: cannot compute the square root of a distribution with a negative mean (-5.0)
+```
+
+> **Note:** For a comprehensive list of all diagnostics emitted by the compiler, check out the [Error Catalog](docs/error-catalog.md).
+
+---
+
+## Head-to-Head: `uncertain` vs. Python's `uncertainties`
+
+Python's popular `uncertainties` package is fantastic, but it operates entirely at *runtime* using linear approximations (the Delta method). 
+
+To see exactly why a compiler-enforced approach is safer and more precise, we've included a script that computes `a * a` where `a = 10.0 ± 2.0`.
+
+Run it yourself:
+```bash
+uv run python scripts/compare_uncertainties.py
+```
+
+**The Output:**
+```text
+1. Naive Hand Calculation (Assuming Independence):
+   Result: 100.00 ± 28.28
+   (DANGEROUS: Silently understates variance by ignoring correlation)
+
+2. Python's `uncertainties` package (a * a):
+   Result: 100.00 ± 40.00
+   (BETTER: Detects correlation, but uses linear Taylor approximation, dropping higher-order terms.)
+
+3. Uncertain DSL (forces `square(a)` at compile time):
+   Result: 100.00 ± 40.40
+   (PERFECT: Compiler caught the reuse, forced explicit intent, and used the exact higher-order formula.)
+```
+
+This single comparison proves the core thesis of the project: `uncertainties` will happily compute a linear approximation of `a * a` without telling you. `uncertain` will throw a **compile-time error**, forcing you to explicitly choose `square(a)`, which in turn applies the *exact* mathematical formula for the variance of a squared distribution.
+
+---
+
+## Language Guide
+
+### Declaring Variables
+All inputs are declared using the built-in `sensor_read()` function. The compiler infers the uncertainty, but you can also provide explicit type annotations to ensure your expectations match reality.
+
+```calc
+// Inferred type
+let width = sensor_read(); 
+
+// Explicitly type-checked distribution
+let length: Measured<Normal(10.0, 1.0)> = sensor_read();
+```
+
+### Math & Operations
+You can safely combine independent measurements using standard arithmetic. The compiler propagates the mean and standard deviation automatically using the Delta-method.
+
+```calc
+let w = sensor_read();
+let h = sensor_read();
+
+let perimeter = w + w + h + h;
+let area = w * h;
+let ratio = w / h;
+let root = sqrt(w);
+```
+
+### Safe Variable Reuse
+If you *must* multiply correlated variables, you must use mathematically safe functions provided by the language to bypass the compiler error:
+
+```calc
+// For perfect self-correlation (squaring a variable)
+let w_squared = square(w);
+
+// If you have a known covariance estimate for two distinct variables
+let correlated_area = correlated(w, h, cov=0.5);
+```
+
+---
+
+## Testing
+
+The project has a highly robust, fuzzed test suite covering lexical analysis, recursive-descent parsing, bidirectional type checking, and hypothesis-driven property tests for the distribution math.
+
+- **Fuzzing**: The parser and typechecker are subjected to thousands of randomly generated inputs and deep AST structures via `hypothesis` to ensure zero unhandled exceptions.
+- **Performance**: The typechecker dependency-union performance is strictly validated against large generated programs.
+
+To run the full test suite:
+```bash
+# Windows
+.\test.bat
+
+# Linux/macOS
+uv run pytest tests/
+```
+
+To run the Monte Carlo simulation cross-validation (which proves our analytic Delta-method formulas match empirical random sampling):
+```bash
+uv run python scripts/monte_carlo_report.py
+```

uncertain_lang-0.1.0/README.md

@@ -0,0 +1,182 @@
+# Uncertain
+
+*A statically-typed arithmetic DSL where every value's type encodes its distributional uncertainty — and the compiler proves how that uncertainty compounds.*
+
+## Why Uncertain?
+
+When you write equations for physical measurements, sensor data, or statistical variables, those values are almost never exact—they are probability distributions. 
+
+If you reuse a variable in a normal programming language without explicitly tracking its mathematical correlation (e.g. `a * a`), your calculated variance will be silently understated, leading to overconfidence in faulty data. 
+
+**`Uncertain` catches these correlation bugs at compile-time by enforcing dependency tracking in its type system.**
+
+---
+
+## Quick Start
+
+### Prerequisites
+- [uv](https://astral.sh/uv/) (Fast Python package and environment manager)
+- Python 3.12+
+
+### Installation
+
+The compiler is available on PyPI. You can install it globally via `pip` or `uv`:
+```bash
+pip install uncertain
+# or
+uv tool install uncertain
+```
+
+If you want to install from source:
+```bash
+git clone https://github.com/yourusername/uncertain.git
+cd uncertain
+pip install .
+```
+
+### Running Scripts
+
+Run an example calculation using the newly installed CLI:
+```bash
+uncertain examples/my_experiment.calc
+```
+
+---
+
+## The Hero Demo: Catching Correlation Bugs
+
+Consider this simple program:
+
+```calc
+let a = sensor_read();
+let variance_est = a * a;
+```
+
+Running `uncertain` on this file immediately catches the hidden dependency reuse:
+
+```text
+error: uncertain reuse without correlation annotation
+  --> line 2:20
+   |
+ 2 | let variance_est = a * a;
+   |                    ^^^^^ `a` appears twice in this product
+   |
+   = note: treating repeated occurrences of `a` as independent understates
+     the true variance of the result.
+   = help: use `square(a)` for the correct self-product variance formula,
+     or wrap with `correlated(..., ..., cov = ...)` if you have an explicit
+     covariance estimate.
+```
+
+### Catching Runtime Math Errors at Compile Time
+Beyond type checking, `uncertain` uses the same beautiful diagnostic system to catch mathematical domain errors before your program even evaluates. For example, taking the square root of a distribution with a negative mean:
+
+```calc
+let a = sensor_read() - 15.0;
+let b = sqrt(a);
+```
+
+Yields a pinpointed math-domain error:
+```text
+error: math domain error
+  --> line 2:9
+   |
+ 2 | let b = sqrt(a);
+   |         ^^^^^^^ invalid operation
+   |
+   = note: cannot compute the square root of a distribution with a negative mean (-5.0)
+```
+
+> **Note:** For a comprehensive list of all diagnostics emitted by the compiler, check out the [Error Catalog](docs/error-catalog.md).
+
+---
+
+## Head-to-Head: `uncertain` vs. Python's `uncertainties`
+
+Python's popular `uncertainties` package is fantastic, but it operates entirely at *runtime* using linear approximations (the Delta method). 
+
+To see exactly why a compiler-enforced approach is safer and more precise, we've included a script that computes `a * a` where `a = 10.0 ± 2.0`.
+
+Run it yourself:
+```bash
+uv run python scripts/compare_uncertainties.py
+```
+
+**The Output:**
+```text
+1. Naive Hand Calculation (Assuming Independence):
+   Result: 100.00 ± 28.28
+   (DANGEROUS: Silently understates variance by ignoring correlation)
+
+2. Python's `uncertainties` package (a * a):
+   Result: 100.00 ± 40.00
+   (BETTER: Detects correlation, but uses linear Taylor approximation, dropping higher-order terms.)
+
+3. Uncertain DSL (forces `square(a)` at compile time):
+   Result: 100.00 ± 40.40
+   (PERFECT: Compiler caught the reuse, forced explicit intent, and used the exact higher-order formula.)
+```
+
+This single comparison proves the core thesis of the project: `uncertainties` will happily compute a linear approximation of `a * a` without telling you. `uncertain` will throw a **compile-time error**, forcing you to explicitly choose `square(a)`, which in turn applies the *exact* mathematical formula for the variance of a squared distribution.
+
+---
+
+## Language Guide
+
+### Declaring Variables
+All inputs are declared using the built-in `sensor_read()` function. The compiler infers the uncertainty, but you can also provide explicit type annotations to ensure your expectations match reality.
+
+```calc
+// Inferred type
+let width = sensor_read(); 
+
+// Explicitly type-checked distribution
+let length: Measured<Normal(10.0, 1.0)> = sensor_read();
+```
+
+### Math & Operations
+You can safely combine independent measurements using standard arithmetic. The compiler propagates the mean and standard deviation automatically using the Delta-method.
+
+```calc
+let w = sensor_read();
+let h = sensor_read();
+
+let perimeter = w + w + h + h;
+let area = w * h;
+let ratio = w / h;
+let root = sqrt(w);
+```
+
+### Safe Variable Reuse
+If you *must* multiply correlated variables, you must use mathematically safe functions provided by the language to bypass the compiler error:
+
+```calc
+// For perfect self-correlation (squaring a variable)
+let w_squared = square(w);
+
+// If you have a known covariance estimate for two distinct variables
+let correlated_area = correlated(w, h, cov=0.5);
+```
+
+---
+
+## Testing
+
+The project has a highly robust, fuzzed test suite covering lexical analysis, recursive-descent parsing, bidirectional type checking, and hypothesis-driven property tests for the distribution math.
+
+- **Fuzzing**: The parser and typechecker are subjected to thousands of randomly generated inputs and deep AST structures via `hypothesis` to ensure zero unhandled exceptions.
+- **Performance**: The typechecker dependency-union performance is strictly validated against large generated programs.
+
+To run the full test suite:
+```bash
+# Windows
+.\test.bat
+
+# Linux/macOS
+uv run pytest tests/
+```
+
+To run the Monte Carlo simulation cross-validation (which proves our analytic Delta-method formulas match empirical random sampling):
+```bash
+uv run python scripts/monte_carlo_report.py
+```

uncertain_lang-0.1.0/docs/error-catalog.md

@@ -0,0 +1,91 @@
+# Uncertain Error Catalog
+
+This catalog documents the structured diagnostics emitted by the `uncertain` compiler and typechecker. Every error is designed to pinpoint the exact location of the issue and provide actionable help.
+
+## `uncertain-reuse`
+**Description:** The intellectual centerpiece of the language. This error is triggered when a variable (representing a probability distribution) appears in both operands of a product or ratio without an explicit correlation annotation. Treating reused variables as independent understates the true variance of the result.
+
+**Example:**
+```
+let x = Normal(10.0, 2.0);
+let y = x * x;
+```
+
+**Diagnostic Output:**
+```text
+error: uncertain reuse without correlation annotation
+  --> line 2:9
+   |
+ 2 | let y = x * x;
+   |         ^^^^^ `x` appears twice in this product
+   |
+   = note: treating repeated occurrences of `x` as independent understates
+     the true variance of the result.
+   = help: use `square(x)` for the correct self-product variance formula,
+     or wrap with `correlated(..., ..., cov = ...)` if you have an explicit
+     covariance estimate.
+```
+
+---
+
+## `undefined-var`
+**Description:** Emitted when a variable is referenced before it has been defined using a `let` binding.
+
+**Example:**
+```
+let y = x + 1.0;
+```
+
+**Diagnostic Output:**
+```text
+error: undefined variable `x`
+  --> line 1:9
+   |
+ 1 | let y = x + 1.0;
+   |         ^ not found in scope
+   |
+   = note: `x` must be declared with `let` before use.
+```
+
+---
+
+## `type-mismatch`
+**Description:** Emitted when the user provides an explicit type annotation (e.g., `Normal(mean, stddev)`) for a `let` binding, but the typechecker infers a distribution with a different mean or standard deviation.
+
+**Example:**
+```
+let a: Normal(10.0, 0.0) = 5.0 + 4.0;
+```
+
+**Diagnostic Output:**
+```text
+error: type annotation mismatch
+  --> line 1:1
+   |
+ 1 | let a: Normal(10.0, 0.0) = 5.0 + 4.0;
+   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ inferred type does not match annotation
+   |
+   = note: the distribution computed by the typechecker differs from the explicit type annotation.
+```
+
+---
+
+## `math-domain-error`
+**Description:** Emitted during typechecking/evaluation when an invalid mathematical operation is performed on a distribution, such as dividing by a distribution with a zero mean, or attempting to take the square root of a distribution with a negative mean.
+
+**Example:**
+```
+let a = Normal(-5.0, 1.0);
+let b = sqrt(a);
+```
+
+**Diagnostic Output:**
+```text
+error: math domain error
+  --> line 2:9
+   |
+ 2 | let b = sqrt(a);
+   |         ^^^^^^^ invalid operation
+   |
+   = note: cannot compute the square root of a distribution with a negative mean (-5.0)
+```

uncertain_lang-0.1.0/examples/bad_math.calc

@@ -0,0 +1,2 @@
+let a = sensor_read() - 15.0;
+let b = sqrt(a);

uncertain_lang-0.1.0/examples/my_experiment.calc

@@ -0,0 +1,25 @@
+// my_experiment.calc
+
+// Let's say we have three sensors reading some physical properties
+let width = sensor_read();
+let length = sensor_read();
+let height = sensor_read();
+
+// We can safely calculate the perimeter and area since width and length are independent
+let perimeter = width + width + length + length;
+let area = width * length;
+
+// We can also calculate volume
+let volume = area * height;
+
+// Let's say we want the square of the height. 
+// Using `height * height` will throw a compiler error because we're reusing the same variable!
+// Instead, we use the mathematically safe `square()` function:
+let height_squared = square(height);
+
+// And we can take the square root of a measurement
+let root_width = sqrt(width);
+
+// If we know two measurements are correlated (e.g. from the same faulty batch of sensors),
+// we can safely multiply them by explicitly providing the covariance:
+let correlated_area = correlated(width, length, cov=0.5);