-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
85a2904
commit 6a5582f
Showing
1 changed file
with
27 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,27 @@ | ||
# Semstrings | ||
# Semstrings | ||
|
||
The core idea behind MT-LLM is that if the program has been written in a readable manner, with type-safety, an LLM would be able to understand the task required to be performed using _meaning_ embedded within the code. | ||
|
||
However, there are instanced where this is not the case for all instances. Hence, a new _meaning_ insertion code abstraction called "**semstrings**" has been introduced in MT-LLM. | ||
|
||
## Where code is not meaningful enough! | ||
|
||
Lets look into an instance where the existing code constructs are not sufficient to describe the meaning of the code for an LLM. | ||
|
||
```python | apple.jac | ||
import:py from mtllm.llms, OpenAI; | ||
|
||
glob llm = OpenAI(); | ||
|
||
obj item | ||
|
||
|
||
``` | ||
|
||
|
||
- Recap the core idea behind MTLLM. | ||
- Show an example where existing code abstractions are not sufficient for embedding meaning in code. | ||
- Introduce semstrings | ||
- Show same example with semstrings | ||
- Show possible semstring insertion points | ||
- where not to use semstring |