lagergren

Pyright strict-mode real-bug audit — A/B/C classification

Follow-up to the original strict-mode real-bug audit attached to PR #2291. Strict mode is not enabled in the PR — this is a one-off audit run by temporarily flipping typeCheckingMode = "strict" and reverting before commit.

The original audit listed 187 primary error sites for the two remaining real-bug rules after reportIndexIssue was eliminated in commit 4f0e2237b:

• 161 × reportUnnecessaryComparison
• 26 × reportConstantRedefinition

This report classifies each site into one of three buckets:

lagergren

This section contains various documents and resources for AI based coding.

AI Coding with Claude Code: A Practical Guide

This guide covers how to get the most out of Claude Code for software engineering. Whether you're a seasoned developer or just starting out, these patterns will help you work more effectively.

---

Table of Contents

lagergren

Language Support for XTC (Ecstasy)

Executive Summary

This document outlines a comprehensive plan to create IDE-independent language support for XTC (Ecstasy), leveraging modern protocols like LSP, DAP, and TextMate grammars to provide syntax highlighting, code intelligence, debugging, and more across multiple IDEs.

Table of Contents

1. Understanding XTC/Ecstasy
2. Current State of Tooling

lagergren

~/src/zombiesnack compose-cleanup *1 !4 ?1 ❯ time pyright                                                                                                                                                                                                                                               х INT Py thaum marcus@thaum 10:04:55
WARNING: there is a new pyright version available (v1.1.359 -> v1.1.361).
Please install the new version or set PYRIGHT_PYTHON_FORCE_VERSION to `latest`

/home/marcus/src/zombiesnack/src/camera/femtomega/camerasettings.py
  /home/marcus/src/zombiesnack/src/camera/femtomega/camerasettings.py:23:12 - error: Operator "/" not supported for types "MatLike" and "int"
    Operator "/" not supported for types "NumPyArrayGeneric" and "int" (reportOperatorIssue)
/home/marcus/src/zombiesnack/src/hyperformer/hyper_aloha/hyperspace_aloha.py
  /home/marcus/src/zombiesnack/src/hyperformer/hyper_aloha/hyperspace_aloha.py:322:20 - error: Operator "|" not supported for types "dict[str, Any]" and "Unk

lagergren

diff --git a/javatools_backend/build.gradle.kts b/javatools_backend/build.gradle.kts
new file mode 100644
index 000000000..63dea1e2f
--- /dev/null
+++ b/javatools_backend/build.gradle.kts
@@ -0,0 +1,33 @@
+/**
+ * Experimental Javatools backend.
+ */
+

lagergren

This is normally not the Docker approach. 
Volumes only exist during runtime, and any changing external source is usually retrieved on volume level and during startup
There may be use cases when you want to clone something from git during the Dockerfile during build, but they are not very common. 
To clone a particular repo as part of the container build do: 

ADD https://api.github.com/repos/org/reponame/git/refs/heads/$GITHUB_BRANCH version.json
RUN git clone --branch $GITHUB_BRANCH --depth=1 https://github.com/org/reponame repo

The verison.json will ADD will create a layer that is invalidated iff $GITHUB_BRANCH is updated, and then, rebuilding the container will
realize that this layer will be regenerated.