Show HN: Fructose – LLM calls as strongly typed functions

Post by thekombustor » Thu, Mar 07, 2024, 7:49 AM UTC

pedrovhb wrote: post #90

babyshake wrote: post #59

Does anyone else get bothered by how this seemingly results in code that won't compile? Instead of this: @ai() def describe(animals: list[str]) -> str: """ Given a list of animals, use one word that'd describe them all. """ it would seem a lot more intuitive to do this: def describe(animals: list[str]) -> str: return ai("""Given a list of animals, use one word that'd describe them all.""", animals)

Technically a function body needs at least one statement. A docstring is just an expression statement (a string), so a function definition with just a docstring is synctatically valid Python. I've seen people say multiline string literals are Python's version of multiline comments, but that's really just convention; it's a noop expression statement. Same as doing def foo(): 4 Which is also an expression statement as…

Post by Sai_ » Thu, Mar 07, 2024, 8:49 AM UTC

Post by [deleted] » Thu, Mar 07, 2024, 12:42 PM UTC

edunteman wrote: post #96

dragonwriter wrote: post #75

Earlier quoted context omitted.

> Yeah the pyright doesn't like the annotated return type not being honored by the empty stub function. I wonder if there's a way to trick it. Python has an existing convention for this (so its not a "trick"), the use of the special value Ellipsis (literal: ...) https://mypy.readthedocs.io/en/stable/stubs.html

Beautiful, this does the trick!! Thanks for the tip. @ai() def stub() -> int: """docstring""" ... # (use ... instead of "pass" in the function body)