Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

decompose class hierarchy of LLM implementations #393

Closed
Intex32 opened this issue Sep 6, 2023 · 0 comments · Fixed by #397
Closed

decompose class hierarchy of LLM implementations #393

Intex32 opened this issue Sep 6, 2023 · 0 comments · Fixed by #397
Assignees

Comments

@Intex32
Copy link
Member

Intex32 commented 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 extends Chat, whereby ChatWithFunctions is not necessarily compatible with Chat, thus modelled incorrectly which can lead to unsupported operations at runtime

@Intex32 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 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
@Intex32 Intex32 self-assigned this Sep 6, 2023
@Intex32 Intex32 linked a pull request Sep 7, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants