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
Why, in your example, is the interface name_to_be_defined(model, template, int) instead of just name_to_be_defined(model, template)? (and, since models is provided by outlines too, wouldn't it make sense to directly provide model.name_to_be_defined(template)?)
Here, template is just any lambda or function that return an str, right? The arguments of the function could likely be inferred (since, iirc, Python is offers a lot of reflexivity) at runtime from the function pointer.
The third argument to name_to_be_defined is the output type. Here we're telling the model we want it to return an integer, which is enforced by structured generation.
(name to be defined)
Following #1226 and #1220 we will be able to implement the following interface:
where fn is a callable object whose arguments are the arguments to the prompt template:
The text was updated successfully, but these errors were encountered: