|
|
|
|
|
by skydhash
22 days ago
|
|
> LLMs are an abstraction just like machine code -> assembly -> C/JVM -> some lang -> LLMs The what is the semantic mapping between <some lang> and LLMs? I know the semantic mapping between maching code and assembly (some light weight syntax manipulation and macros). I know the one between assembly and C (the C abstract machine, which is mostly about the stack and whatever call/ret instructions pair). I know the one between C and something like python (not so much different than the one between C and assembly in mechanism). Please talk about how you go from A LLM prompt to a piece of code in Python and guarantee the intent remains unchanged. |
|
Basically it turns out that code is full of incidental details and what you really want is to verify the important parts, while receiving a guarantee that the vast tail of incidentals is handled "reasonably."