Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original implementation of
TemplateBackend
relied upon thesignature_to_template
function. This would take in adspy.Signature
and return adsp.Template
. However, we would passdspy.Example
into thedsp.Template
and the extract function would returndsp.Example
a different type. Leaving us with two different types ofExample
within a single prediction. To combat this, a newTemplate
primitive was introduced intodspy
to mirror and replace the originaldsp.Template
.I do not expect this current PR to achieve feature parity with the original class, but initial tests have been introduced to mock and mirror the current prompt structure used in
dsp
.Let me know what you think @CyrusOfEden, the last piece I believe to start using the
TemplateBackend
is to fully explore thedo_generate
function dealing with incomplete or inaccurate completions.