sure, lexing and parsing are also one pass in my system, but they're still clearly hierarchically separated; there's no backchannel from the parser to the lexer.
-
-
Other challenges arise from the need to obey Walder-style free theorems / universal properties, as a means of compiler-guaranteed erasure and data hiding. Runtime code can't cheat by asking a type for its metadata; you had to expose it at compile-time via macro.
-
The grand scheme here is a language with no undefined behavior that can run deterministically in a decentralized environment, where in concept everyone in the world is running and verifying a transactional shared state simulation. (No problem, right?)
- 1 more reply
New conversation -
-
-
right - i accepted that as a natural limitation of macros. they can at least know in what lexical scope the name occurs, but that's it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.