vx-lang/Vx

vxc --version prints vxc 0.0.2 for any compiler built from source, because it reads the version in Cargo.toml. A compiler built today from main (git describe: v0.0.2-206-gf1fb0333) gives the same answer as the v0.0.2 release. So a project that uses Vx cannot tell which compiler built its code. glm-vx saves the compiler version next to every file it generates. Its records say vxc 0.0.2 both when built with the release and when built with the compiler from main, even though the two produce different GPU code (PTX) from the same source. Expected: when the compiler is built from a git checkout, --version also includes the commit, for example vxc 0.0.2 (f1fb0333), and marks a build that had uncommitted changes.

A warning or error message says where the problem is with a line and column, but not which file. Some warnings have no location at all. fn unused_param(x: i32, j: i32) -> i32 { return x; } fn after_return(x: i32) -> i32 { return x; let y = x + 1; return y; } vxc warnings.vx --action emit-obj -o w.o prints: Warning[W1009]: Unused function parameter 'j' Warning[W1003] at 7:5: Unreachable code after return, break, or continue Errors look the same: Error[E2001] at 2:12: Undefined variable 'nope'. Only the summary line after it names the file. This matters when a build compiles several files, or a file that imports others. glm-vx builds two files from a script, and its build log has eight Unused function parameter 'table' warnings with nothing to say where any of them are. Expected: every message has file:line:column, like warnings.vx:1:32: Warning[W1009]: Unused function parameter 'j'. That is also the format editors and CI tools know how to turn into links.

Will make it easy to refer to a specific section

e.g., from https://vxlang.org/blog/what-comptime-can-do.html one has to select the full code which is a bit inconvenient.

Only plain decimal literals are accepted. The lexer reads the rest of the literal as a type suffix. fn main() -> i32 { let a : i32 = 0x2A; return a; } Error at 2:34: Unknown element type 'x2A' 0b101010 fails with Unknown element type 'b101010' and 42_000 style literals with Unknown element type '_000_042'. Found by a feature sweep of main at d3a00e8 (debug build, JIT).