You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
decompose class hierarchy of LLM implementations:
from one class per provider → one class per model and it's respective capabilities
Current problem:
you may call functions on a model that the model does not support, as there is only one class per provider that all models use
in particular, ChatWithFunctions extends Chat, whereby ChatWithFunctions is not necessarily compatible with Chat, thus modelled incorrectly which can lead to unsupported operations at runtime
The text was updated successfully, but these errors were encountered:
Intex32
changed the title
decompose class hierarchy of LLM implementations from one class per provider to one class per model and itcapability
decompose class hierarchy of LLM implementations from one class per provider to one class per model and it's respective capabilities
Sep 6, 2023
Intex32
changed the title
decompose class hierarchy of LLM implementations from one class per provider to one class per model and it's respective capabilities
decompose class hierarchy of LLM implementations
Sep 6, 2023
decompose class hierarchy of LLM implementations:
from one class per provider → one class per model and it's respective capabilities
Current problem:
you may call functions on a model that the model does not support, as there is only one class per provider that all models use
in particular,
ChatWithFunctions
extendsChat
, wherebyChatWithFunctions
is not necessarily compatible withChat
, thus modelled incorrectly which can lead to unsupported operations at runtimeThe text was updated successfully, but these errors were encountered: