What if kernel/userland/baremetal restrictions were enforced semantically at compile time?
I’ve been building an experimental LLVM-native systems language called FALCON where deployment profiles ("userland", "kernel", "baremetal") are treated as actual compile-time semantic laws instead of optional conventions.
The compiler validates environment/profile compatibility during IR validation, so invalid combinations fail at compile time rather than relying on runtime assumptions or documentation.
Some core ideas:
- compile-time semantic profiles
- capability-based library enforcement
- environment-aware compilation
- LLVM native codegen
- direct C interoperability
- zero-runtime assumptions for low-level targets
The overall goal is basically:
Python-like ergonomics with native systems-level control and profile-enforced safety boundaries.
Still very early and experimental, but I’d genuinely love feedback from people interested in:
- compilers
- systems programming
- LLVM
- kernel/baremetal tooling
- low-level language design
Repo: