JhonPork

3 ms·

1. 1.▲
   by JhonPork 9mo ago

   It’s similar at a surface level, but the key difference is when the choice is made and what is being selected. #ifdef and libraries still live inside a single execution contract — the compiler parses and reasons about everything, and constr
2. 2.▲
   by JhonPork 9mo ago

   This is fair feedback, and you’re pointing at the main tradeoff intentionally. One clarification that might help: Falcon isn’t multiple frontends or multiple grammars in the usual sense. The parser accepts all code into a single AST, but du
3. 3.▲
   by JhonPork 9mo ago

   Good question the distinction is intentional. Falcon’s profiles are not meant to be “dialects you mix freely” like Rust’s unsafe blocks. They represent different execution contracts, not different safety levels inside the same runtime. In R
4. 4.▲
   by JhonPork 9mo ago

   Profiles are resolved before code generation, not via conditionals. Each top-level item (function, block, impl, import) can be annotated with a profile (userland, kernel, baremetal). During parsing, everything is collected into the AST as u
5. 5.▲
   Experimenting with a Compiled Language

   4 points by JhonPork 9mo ago|8 comments