-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Does Llama 3/3.1 text/instruct support FIM? #320
Comments
LLaMA models, aren’t designed for tasks where you need to fill in gaps in code like CodeLlama can. CodeLlama is tailored for this kind of job—it's great at completing code snippets or filling in missing parts of code. While LLaMA models excel at tasks like generating text and summarizing information, they’re not specifically built for code completion. If your main goal is to handle code fill-ins, you might want to look at CodeLlama or other tools that specialize in that area. |
+1. Would love to get an answer on this. If this is not supported, will there be a codellama 3.1? Thank you. |
LLaMA 3/3.1 currently does not support Fill-in-the-Middle (FIM)
functionality. As for CodeLlama 3.1, there haven't been any official
announcements regarding its release yet. However, given Meta's continued
development in this space, it is possible that future models might include
enhanced features for code and text generation.
…On Sun, 8 Sep, 2024, 10:16 moreward, ***@***.***> wrote:
+1. Would love to get an answer on this. If this is not supported, will
there be a codellama 3.1?
Thank you.
—
Reply to this email directly, view it on GitHub
<#320 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5O2DJOC4EYVBFYQ5VTHMDDZVPJBDAVCNFSM6AAAAABMRE2QUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWGU2DKMRVHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Does Llama 3 or 3.1 (instruct or text models) support fill-in-the-middle like CodeLlama?
(Couldn't find this information on the web so decided to ask here, sorry if it's the wrong place)
The text was updated successfully, but these errors were encountered: