forked from Orchid/orchid
21 lines
929 B
Markdown
21 lines
929 B
Markdown
Decide whether we need patterns at runtime. Maybe macros aren't obligated to return MacTree so destructuring can be done in a safer and easier way?
|
|
|
|
Double-check type and templating logic in the note, it's a bit fishy.
|
|
|
|
Consider whether all macros need to be loaded or the const references could be used to pre-filter for a given let line.
|
|
|
|
## alternate extension mechanism
|
|
|
|
The STD system will have a lot of traffic for trivial operations like algebra, stream IO will likely not be fast enough. A faster system is in order.
|
|
|
|
Ideally, it should reuse `orchid-extension` for message routing and decoding.
|
|
|
|
`orchid-host` accepts extensions as `impl ExtensionPort`
|
|
|
|
## Preprocessor extension
|
|
|
|
The macro system will not be privileged, it can take control from the interpreter via a custom top-level "let" line type.
|
|
|
|
Must actually write macro system as recorded in note
|
|
|
|
Check if any of this needs interpreter, if so, start with that |