chatgpt-ifplatform VS hoogle

It's really an experimental endeavor. I have a Github repo (https://github.com/ChicagoDave/chatgpt-ifplatform), but I'm still changing things all the time. It's very volatile.

Finding the balance between OO principals, Fluid coding capabilities, separating the data, grammar, parser, and world model and then constructing a standard IF library of common IF "things" is like juggling 20 kittens and 10 chainsaws.

Some things are confounding like do I define a container with a boolean property on an object or is a container a subclass of the base Thing? How does that extend to the underlying graph data store? What will queries look like and which solution is more meaningful to authors?

Seriously, 95% of the fun is figuring all of these things out.

Dimensions behave somewhat like a "type system" for math. These dimensional-analysis tricks act like the trick you see in Haskell sometimes, where you can easily guess an implementation of an expression once you know it's type (or e.g. search by type signature https://hoogle.haskell.org/ )

Haskell Spotlight makes vscode a client for hoogle. It isn't too different than jumping into your browser and type https://hoogle.haskell.org/. The main advantage is that you have everything in one place

https://hackage.haskell.org/package/base and https://hoogle.haskell.org are automatically up to date and better searchable than almost any other reference of any other programming language. maintaining a redundant reference that needs to be kept up to date manually is simply stupid.

Ideally like this: https://zio.dev/reference/#concurrency

Or this: https://hoogle.haskell.org/?hoogle=fork

And yeah I get it, it's hard to Google for punctuation operators in languages because it doesn't give useful search results (but not impossible, for example, Haskell has a search engine for documentation that handles symbols/punctuation).

{ "customLocalFormatters.formatters": [ { "command": "make format", "languages": ["haskell"] } ], "emeraldwalk.runonsave": { "commands": [ { "match": "*.hs", "isAsync": true, "cmd": "make retag retag_file=${file}" } ] }, "ghcid.command": "make ghcid", "goto-documentation.customDocs": { "hs": "https://hoogle.haskell.org/?hoogle=${query}" } }

You had a look at Hoogle?

https://hoogle.haskell.org/

For some type signatures there is (are) only one (or only a few) meaningful implementation(s).