Skip to content

Support llguidance #774

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

Closed
wants to merge 1 commit into from
Closed

Support llguidance #774

wants to merge 1 commit into from

Conversation

yujonglee
Copy link
Contributor

Resolves #701

@MarcusDunn
Copy link
Contributor

MarcusDunn commented Jul 21, 2025

Is there a second PR required to expose the guidance APIs?

i.e. what would it take to modify simple to guide output?

Copy link
Contributor

@MarcusDunn MarcusDunn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking into this, I can see why this would be a very cool feature.

However, I don't think this approach will do what you're expecting.

The only place the llguidance API's are exposed is in common/sampling.h, which we do not generate bindings to. I do not want this to change as keeping up to date with the main API is difficult enough as is with as little maintenance effort as this project currently receives.

On the bright side, llguidance is a rust library and I think a llama-cpp-rs + llguidance library would be pretty easy to build and maintain. Building a rust library (llguidance) as part of a c++ library (llama.cpp) to be used by a rust library (llama-cpp-rs) strikes me as the wrong approach.

Unless I'm mistaken I will probably not merge this PR.

@yujonglee
Copy link
Contributor Author

Agreed. Thanks for the input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LLGuidance support with feature flag
2 participants