Add apredict_and_parse to LLM

[timothyasp]

predict_and_parse exists, and it's a nice abstraction to allow for applying output parsers to LLM generations. And async is very useful.

As an aside, the difference between call/acall, predict/apredict and generate/agenerate isn't entirely
clear to me other than they all call into the LLM in slightly different ways.

Is there some documentation or a good way to think about these differences?

One thought:

output parsers should just work magically for all those LLM calls. If the output_parser arg is set on the prompt, the LLM has access, so it seems like extra work on the user's end to have to call output_parser.parse

If this sounds reasonable, happy to throw something together. @hwchase17

[hwchase17]

output parsers should just work magically for all those LLM calls. If the output_parser arg is set on the prompt, the LLM has access, so it seems like extra work on the user's end to have to call output_parser.parse

If this sounds reasonable, happy to throw something together. @hwchase17

yeah we thought about this a bit when revamping output parsers... tldr we want to hold off for now, but not against adding in the future