Skip to content
This repository was archived by the owner on Nov 15, 2026. It is now read-only.

Tala 0.5.2 (previous numbering)

Choose a tag to compare

@Leitwolf11 Leitwolf11 released this 12 Oct 04:24
ad930c5

Visual X# is now Tala

The language and its tools have new names. The entries below and those of
earlier releases keep the names they were written with.

  • The language is Tala and its sources end in .tala (was .vxs).
  • The compiler is talac (was vxs), the REPL is tali (was vxsi) and
    takes --eval (was -Eval), the formatter is talafmt, the linter is
    talalint, the language server is tala-analyzer, and the build system
    and package manager is Tazel, whose project file is BUILD.kts, whose
    lockfile is LOCK.sqlite3 and whose plugin cache is .tazel/plugins.
  • Directories: Compiler/ is Talac/, ProjectSystem/ is Tazel/, and
    Analyzer/, Formatter/, Linter/ are Ecosystem/tala-analyzer/,
    Ecosystem/talafmt/, Ecosystem/talalint/.
  • C++ headers are included as Progmasoft/Tala/... and the namespace is
    Progmasoft::Tala; the Haskell modules are Progmasoft.Tala.*,
    Progmasoft.Talafmt.*, Progmasoft.Talalint.* and
    Progmasoft.TalaAnalyzer.*; the Cabal packages are tala-syntax,
    tala-frontend, tala-core, tala-compiler, tala-analyzer, talafmt
    and talalint; the Kotlin packages are com.progmasoft.tazel.*,
    com.progmasoft.talafmt, com.progmasoft.talalint and
    com.progmasoft.tala.analyzer; the Go module is
    github.com/Progmasoft/tala/helpers.
  • Binary names: the frontend library is tala-frontend, the runtime library
    is tala-runtime.lib or libtala-runtime.a, exported C symbols begin with
    tala_, and environment variables and macros begin with TALA_.
  • Diagnostic codes begin with TA (TAT0080 was VXT0080), and the magic
    numbers of the wire formats are TACR, TACP, TAPP, TAMM and TADC.
    Artifacts written by an earlier compiler are not read.
  • The C interface is TCI, the Tala C Interface (was VXCI).
  • Not yet changed: the options of talac still have the -Option form and a
    native executable still ends in .vxse.

Compiler

  • A callable parameter written without a type, as in \x -> x + 1, is
    reported as TAT0082. Its type was left unknown, since taking it from the
    place that expects the callable is not implemented, and the program was
    refused only by the LLVM lowering, with an error about the backend and no
    place in the source. Coverage-guided fuzzing found it; the program is kept
    as a seed.
  • A local whose value is computed by need no longer makes a long chain of
    operators slow to compile. The lowering looked through the whole operand
    tree again at every operator while such a local was in scope, so the time
    grew with the cube of the length of the chain: a chain of 3 940 terms that
    held one division did not finish in five minutes and now takes about a
    second. The lowered program is the same. Coverage-guided fuzzing found it
    as a timeout; a shorter program of the same shape is kept as a seed.

Native executables

  • vxs build and vxs run produce a native executable on Linux and macOS,
    as they did on Windows. The program is linked by the C compiler of the
    system with libvxs-runtime.a, which stands beside the compiler, and with
    the C library; objects for ELF and Mach-O are position independent. A
    program that stops is reported by vxs run as 128 and the number of the
    signal that ended it.

Command line

  • -File with a path that is not well-formed UTF-8 is reported as an invalid
    value. On Windows the conversion to a native path threw, and vxs, which
    is built without exceptions, stopped without a diagnostic. The new
    command-line seeds found it in their first campaign.

Verification and tooling

  • Documents/abi-manifest.json states the binary interfaces of the compiler in
    one place: the C functions of the frontend library and of the runtime, the
    numbers they exchange, the versions of the four wire formats, and how an
    executable is entered and linked. verify-abi reads every entry back from
    the header or source that defines it and fails on a difference in either
    direction; the compiler workflows run it.
  • prebuild and optional-packages support Debian 13, with apt as on
    Ubuntu. Debian's own repositories have no .NET SDK; optional-packages
    says so there and installs the rest.
  • cross-platform-test checks a branch on the platforms a developer is not
    sitting at, before a pull request exists. ci starts the compiler
    workflows for the current branch, on real Windows, macOS and Linux
    machines, and can follow them to their end; the workflows can now be
    started by hand for that. run uses Podman containers on the developer's
    machine instead, for Ubuntu 26.04 and Fedora 43: macOS and Windows do not
    run in a container and are listed with the reason. prebuild now checks
    for and installs Podman.
  • The fuzz corpora are larger. The lexer, parser and source targets are seeded
    with the Visual X# sources the repository already holds, more than two
    hundred programs, read where they are. The command-line, project, REPL,
    ownership and differential corpora grow from 13 seeds to 107, written in the
    form each harness reads; the one command-line seed there was separated its
    arguments with line breaks, which the harness does not split on, and is
    replaced.
  • CodeQL analyses C and C++ from a real build as well. The analysis without a
    build, which runs for every pull request, holds every native source but
    resolved 30 percent of their includes; the new c-cpp-traced job observes
    a Bazel compilation of every native target. It runs for the default
    branch, weekly, on request, and for a pull request labelled
    codeql-traced.
  • develop analyze runs the Clang Static Analyzer over every first-party
    C++ translation unit with the command Bazel compiles it with: the stable
    checkers that have to be asked for beside the default ones, and a set of
    checkers still in development whose findings are reported and do not fail
    the run. A new workflow runs it for every pull request and uploads the
    findings, with the path of each, to code scanning.
  • Every command of helpers/ defines its command line with Cobra.
    verify-benchmarks and verify-examples take the checkout as --root;
    their earlier -Root and -Help are rejected. prebuild and
    optional-packages take check or install as a command, in lower case,
    and print their help when no command is given. verify-docs rejects
    arguments it used to ignore. An invocation a command does not understand
    fails before it reads, probes or installs anything.
  • develop fuzz, fuzz-stress and fuzz-thread take --seconds, --jobs,
    --corpus and --target, each beside the environment variable of the same
    meaning; VXS_FUZZ_TARGETS is new. develop fuzz-targets lists the targets
    and their limits. A selection that names an unknown target is refused before
    a build.
  • develop sanitizers lists what each sanitizer kind is on the host, and
    develop sanitize all runs every checker the host has and reports each.
  • develop benchmark takes --output, --filter, --repetitions,
    --native-only and --haskell-only. develop benchmark-report prints a
    result set as a table, and develop benchmark-compare sets one against
    another and fails when a benchmark became slower than a threshold.
  • optional-packages supports the hosts prebuild supports: it now installs
    on Ubuntu 26.04 LTS with apt and on Fedora 43 with dnf as well.